Re: Todays git migration results - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Todays git migration results
Date
Msg-id AANLkTimO4he_Vt1gzaaCyg7JtEFdWkqfmj_Q+jVb7CG4@mail.gmail.com
Whole thread Raw
In response to Re: Todays git migration results  (Alex Hunsaker <badalex@gmail.com>)
Responses Re: Todays git migration results  (Alex Hunsaker <badalex@gmail.com>)
List pgsql-hackers
On Tue, Aug 17, 2010 at 11:46 AM, Alex Hunsaker <badalex@gmail.com> wrote:
> On Tue, Aug 17, 2010 at 09:21, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Tue, Aug 17, 2010 at 10:51 AM, Alex Hunsaker <badalex@gmail.com> wrote:
>>> On Tue, Aug 17, 2010 at 08:17, Robert Haas <robertmhaas@gmail.com> wrote:
>>>> /me is very sorry master.  Please beat your unworthy servant only
>>>> lightly...  or alternatively, buy me a faster machine.
>>>
>>> Well, I might be able to afford a beer.
>>
>> Done!
>
> Well on 2nd thought, maybe not... If people start collecting I'll be
> broke (notably I owe tom quite a few :-).

Cheapskate.

> Anyway find below version that passes any arguments through to git-log.

Yeah, I don't think I want to go that route.  Arbitrary user-specified
arguments to git-log might not be (probably aren't) sane in this
context, and there's also a chance that might want to have arguments
that are handled internally by the script, rather than passed through.But I do agree that passing --since through is
sensible.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Todays git migration results
Next
From: Peter Eisentraut
Date:
Subject: Re: Python 2.7 deprecated the PyCObject API?