Jeff King writes:
> Agreed. I just posted a patch series that gives you --pretty lua
> support, though I haven't convinced myself it's all that exciting yet. I
> think it would be nicer for grepping, where the conditionals read more
> like regular code. Something like:
>
> git log --lua-filter=
Jeff King venit, vidit, dixit 25.09.2012 02:42:
> On Sun, Sep 23, 2012 at 05:07:04PM +0200, Michael J Gruber wrote:
>
>>> If we linked with an embeddable scripting language interpreter
>>> (e.g. lua, tcl, guile, ...), it may be a more practical enhancement,
>>> though.
>>>
>>
>> Yes, the idea is "
On Sun, Sep 23, 2012 at 05:07:04PM +0200, Michael J Gruber wrote:
> > If we linked with an embeddable scripting language interpreter
> > (e.g. lua, tcl, guile, ...), it may be a more practical enhancement,
> > though.
> >
>
> Yes, the idea is "extend, don't embed" the other way round, so to say.
On Sat, Sep 22, 2012 at 01:23:56PM -0700, Junio C Hamano wrote:
> Michael J Gruber writes:
>
> > On my mental scratch pad (yeah, that's where the bald spots are) I have
> > the following more general idea to enhance the revision parser:
> >
> > --limit-run=
Junio C Hamano venit, vidit, dixit 22.09.2012 22:23:
> Michael J Gruber writes:
>
>> On my mental scratch pad (yeah, that's where the bald spots are) I have
>> the following more general idea to enhance the revision parser:
>>
>> --limit-run=
Michael J Gruber writes:
> On my mental scratch pad (yeah, that's where the bald spots are) I have
> the following more general idea to enhance the revision parser:
>
> --limit-run=
Junio C Hamano venit, vidit, dixit 22.09.2012 01:51:
> Jeff King writes:
>
>> I think people have provided sane techniques for doing this with a
>> pipeline. But there is really no reason not to have --grep-notes, just
>> as we have --grep. It's simply that nobody has implemented it yet (and
>>
Joshua Jensen writes:
> Background: To tie Perforce changelists to Git commits, I add a note
> to a commit with the form "P4@123456". Later, I use the note to sync
> down the closest Perforce changelist matching the Git commit.
I noticed that nobody brought this up, but probably it should not b
Jeff King writes:
> I think people have provided sane techniques for doing this with a
> pipeline. But there is really no reason not to have --grep-notes, just
> as we have --grep. It's simply that nobody has implemented it yet (and
> nobody is working on it as far as I know). It would actually
On Fri, Sep 21, 2012 at 03:10:40PM -0600, Joshua Jensen wrote:
> - Original Message -
> From: Johannes Sixt
> Date: 9/21/2012 2:50 PM
> >The trick is to pipe 'git log' output into another process that reads no
> >more than it needs and exits. Then 'git log' dies from SIGPIPE before it
> >p
- Original Message -
From: Johannes Sixt
Date: 9/21/2012 2:50 PM
The trick is to pipe 'git log' output into another process that reads no
more than it needs and exits. Then 'git log' dies from SIGPIPE before it
processed all 1000 commits because its down-stream has gone away.
For example
Am 21.09.2012 22:25, schrieb Joshua Jensen:
> - Original Message -
> From: Junio C Hamano
> Date: 9/21/2012 2:04 PM
>> Joshua Jensen writes:
>>
Is there any particular reason you do that as two separate steps?
It would feel more natural, at least to me, to do something along
- Original Message -
From: Junio C Hamano
Date: 9/21/2012 2:04 PM
Joshua Jensen writes:
Is there any particular reason you do that as two separate steps?
It would feel more natural, at least to me, to do something along
the lines of
git log --show-notes=p4notes -1000
Thanks
Joshua Jensen writes:
>> Is there any particular reason you do that as two separate steps?
>> It would feel more natural, at least to me, to do something along
>> the lines of
>>
>> git log --show-notes=p4notes -1000
>>
>>
> Thanks for the reply.
>
> I did not make clear above that I want to
- Original Message -
From: Andreas Schwab
Date: 9/21/2012 9:10 AM
Joshua Jensen writes:
Background: To tie Perforce changelists to Git commits, I add a note to a
commit with the form "P4@123456". Later, I use the note to sync down the
closest Perforce changelist matching the Git commi
- Original Message -
From: Junio C Hamano
Date: 9/21/2012 11:21 AM
Joshua Jensen writes:
Background: To tie Perforce changelists to Git commits, I add a note
to a commit with the form "P4@123456". Later, I use the note to sync
down the closest Perforce changelist matching the Git comm
Joshua Jensen writes:
> Background: To tie Perforce changelists to Git commits, I add a note
> to a commit with the form "P4@123456". Later, I use the note to sync
> down the closest Perforce changelist matching the Git commit.
>
> I search for these notes by getting a list of revisions:
>
>
Joshua Jensen writes:
> Background: To tie Perforce changelists to Git commits, I add a note to a
> commit with the form "P4@123456". Later, I use the note to sync down the
> closest Perforce changelist matching the Git commit.
>
> I search for these notes by getting a list of revisions:
>
>
Background: To tie Perforce changelists to Git commits, I add a note to
a commit with the form "P4@123456". Later, I use the note to sync down
the closest Perforce changelist matching the Git commit.
I search for these notes by getting a list of revisions:
git rev-list --max-count=100
19 matches
Mail list logo
