Re: [git-users] bug with --max-count option in "git rev-list" command

2018-09-13 Thread Daniel Burtman
Thank you!

On Thursday, September 13, 2018 at 12:45:22 PM UTC-4, Konstantin Khomoutov 
wrote:
>
> On Thu, Sep 13, 2018 at 09:13:57AM -0700, Daniel Burtman wrote: 
>
> Hi! 
>
> > I’m running git rev-list command and getting usage message instead of 
> > normal output: 
> > 
> > git rev-list --max-count=3 
> > 
> > usage: git rev-list [OPTION] ... [ -- paths... ] 
> > 
> >   limiting output: 
> > 
> > --max-count= 
> > 
> > --max-age= 
> > 
> > --min-age= 
> > 
> > --sparse 
> > 
> > --no-merges 
> > 
> > --min-parents= 
> > 
> > Same option works fine with git log. 
> > 
> > git log --max-count=3 
> > 
> > commit 9e4734508472b9eb7358ef2e9d46645da84c40a9 (*HEAD ->* *develop*, 
> > *origin/develop*, *origin/HEAD*) 
> > 
> > . . . . 
> > 
> > I’m using Git version 2.19.0 on MacOS High Sierra 10.13.6 
> > 
> > Any ideas, suggestions regarding whether this has been noticed and ETA 
> for 
> > resolution? 
>
> I reckon the simple difference is that contrary to `git log`, 
> `git rev-list` makes no implicit assumption about what "ref" (a Git's 
> parlance for anything which references a commit - such as a branch or a 
> tag). That is, if you don't tell `git log` what commit(s) to start 
> traversing the history graph from, it assumes the HEAD ref, but 
> `git rev-list` expects one or more things resolvable to a commit or one 
> or more special options which allow to specify a group of refs: "--all", 
> "--branches[=pattern]" and/or "--tags[=pattern]". 
>
> So your encantation for `git rev-list` would be 
>
> $ git rev-list --max-count=3 HEAD 
>
> Please consult `git help rev-list` and `git help revisions` for more 
> info. 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[git-users] Re: bug with --max-count option in "git rev-list" command

2018-09-13 Thread Daniel Burtman
Thank you!
That was indeed the missing part.
Appreciate your responses.

On Thursday, September 13, 2018 at 12:13:57 PM UTC-4, Daniel Burtman wrote:
>
> Hi there
>
>  
>
> I’m running git rev-list command and getting usage message instead of 
> normal output:
>
>  
>
> git rev-list --max-count=3
>
> usage: git rev-list [OPTION] ... [ -- paths... ]
>
>   limiting output:
>
> --max-count=
>
> --max-age=
>
> --min-age=
>
> --sparse
>
> --no-merges
>
> --min-parents=
>
>  
>
> Same option works fine with git log.
>
>  
>
> git log --max-count=3
>
> commit 9e4734508472b9eb7358ef2e9d46645da84c40a9 (*HEAD ->* *develop*, 
> *origin/develop*, *origin/HEAD*)
>
> . . . .
>
>  
>
> I’m using Git version 2.19.0 on MacOS High Sierra 10.13.6
>
>  
>
> Any ideas, suggestions regarding whether this has been noticed and ETA for 
> resolution?
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [git-users] bug with --max-count option in "git rev-list" command

2018-09-13 Thread Konstantin Khomoutov
On Thu, Sep 13, 2018 at 09:13:57AM -0700, Daniel Burtman wrote:

Hi!

> I’m running git rev-list command and getting usage message instead of 
> normal output:
> 
> git rev-list --max-count=3
> 
> usage: git rev-list [OPTION] ... [ -- paths... ]
> 
>   limiting output:
> 
> --max-count=
> 
> --max-age=
> 
> --min-age=
> 
> --sparse
> 
> --no-merges
> 
> --min-parents=
> 
> Same option works fine with git log.
> 
> git log --max-count=3
> 
> commit 9e4734508472b9eb7358ef2e9d46645da84c40a9 (*HEAD ->* *develop*, 
> *origin/develop*, *origin/HEAD*)
> 
> . . . .
> 
> I’m using Git version 2.19.0 on MacOS High Sierra 10.13.6
> 
> Any ideas, suggestions regarding whether this has been noticed and ETA for 
> resolution?

I reckon the simple difference is that contrary to `git log`,
`git rev-list` makes no implicit assumption about what "ref" (a Git's
parlance for anything which references a commit - such as a branch or a
tag). That is, if you don't tell `git log` what commit(s) to start
traversing the history graph from, it assumes the HEAD ref, but
`git rev-list` expects one or more things resolvable to a commit or one
or more special options which allow to specify a group of refs: "--all",
"--branches[=pattern]" and/or "--tags[=pattern]".

So your encantation for `git rev-list` would be

$ git rev-list --max-count=3 HEAD

Please consult `git help rev-list` and `git help revisions` for more
info.


-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[git-users] Re: bug with --max-count option in "git rev-list" command

2018-09-13 Thread Philip Oakley
On Thursday, September 13, 2018 at 5:13:57 PM UTC+1, Daniel Burtman wrote:

> Hi there
>
>  
>
> I’m running git rev-list command and getting usage message instead of 
> normal output:
>
>  
>
> git rev-list --max-count=3
>
> usage: git rev-list [OPTION] ... [ -- paths... ]
>
>   limiting output:
>
> --max-count=
>
> --max-age=
>
> --min-age=
>
> --sparse
>
> --no-merges
>
> --min-parents=
>
>  
>
> Same option works fine with git log.
>
>  
>
> git log --max-count=3
>
> commit 9e4734508472b9eb7358ef2e9d46645da84c40a9 (*HEAD ->* *develop*, 
> *origin/develop*, *origin/HEAD*)
>
> . . . .
>
>  
>
> I’m using Git version 2.19.0 on MacOS High Sierra 10.13.6
>
>  
>
> Any ideas, suggestions regarding whether this has been noticed and ETA for 
> resolution?
>


You need the  argument for rev-list (IIUC), while HEAD is assumed 
with log.
-- 
Philip
 

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[git-users] bug with --max-count option in "git rev-list" command

2018-09-13 Thread Daniel Burtman


Hi there

 

I’m running git rev-list command and getting usage message instead of 
normal output:

 

git rev-list --max-count=3

usage: git rev-list [OPTION] ... [ -- paths... ]

  limiting output:

--max-count=

--max-age=

--min-age=

--sparse

--no-merges

--min-parents=

 

Same option works fine with git log.

 

git log --max-count=3

commit 9e4734508472b9eb7358ef2e9d46645da84c40a9 (*HEAD ->* *develop*, 
*origin/develop*, *origin/HEAD*)

. . . .

 

I’m using Git version 2.19.0 on MacOS High Sierra 10.13.6

 

Any ideas, suggestions regarding whether this has been noticed and ETA for 
resolution?

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.