Re: Quickly searching for a note
- From
Joshua Jensen <jjensen@workspacewhiz.com>
- Date
- Sep 21, 2012, 20:25 UTC
- Message-ID
- <505CCD2A.8020003@workspacewhiz.com>
- In-Reply-To
- <7vtxur3zxi.fsf@alter.siamese.dyndns.org>
----- Original Message ----- From: Junio C Hamano Date: 9/21/2012 2:04 PM
Show 21 quoted lines
> Joshua Jensen <jjensen@workspacewhiz.com> 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 stop looking when I find the >> first commit that has the note. >> >> In the case of 'git log --show-notes=p4notes -1000', Git will process >> and hand me the log output for 1,000 commits. It is rare I need to >> walk that deep. > I simply matched it with your initial "rev-list --max-count=1000". > The "log" command pages and you can hit 'q' once you saw enough (in > other words, you do not have to say -1000). >
This is run via script without user intervention. Presumably, Git will do 1,000 commits of work when it may only need to do 1 or 5 or 10?
-Josh