Uwe Brauer <o...@mat.ucm.es> writes:

> On the other hand it is possible to use the following git command to
> obtain a more or less similar information
>
> git log --graph --color=always --all --decorate --pretty=short | git name-rev
> --stdin | less -R

It's more less than more more similar information. :-)

git name-rev 921af2f1 will, in case that commit is not the head of some
branch or a tag, show something like master~19 meaning the 19th parent
of the current master branch's HEAD.  When another commit is made on
master, the very same commit will then be master~20.  So it's a totally
unstable numbering in contrast to revision numbers known from other
VCSs.  It's only value is that it's easier to type than a hash.

> That works fine for small repositories but for GNU emacs this command
> leads, at least on my 5 year old Laptop to a core dump.

Works fine for me, and my laptop is 2 years older. ;-)

> I presume the reason is that git «calculates» these numbers on the
> fly.

Yes, probably.

> So a simple solution to the problem would be to reduce the numbers of
> name-rev git shall calculate.
>
> I cannot find any option doing this.
>
> Any idea what to do?

Do you really need to show the log back into the 80ies?  If not, use
something like "--since 2years" in your git log invocation.

Bye,
Tassilo

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/878rk4hxqw.fsf%40gnu.org.

Reply via email to