Re: [PATCH] bisect: Store first bad commit as comment in log file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Torstein Hegge <hegge@xxxxxxxxxxx> writes:

> I was wondering why "git grep show-ref *.sh" gave so few users. It looks
> like rev-parse is more common.

It is primarily because show-ref is slightly newer.  When you have a
full refname (e.g. refs/bisect/bad) and not an arbitrary object name
that is spelled in a random way (e.g. master~24):

       show-ref --verify refs/bisect/bad

is a perfectly valid way to make sure it _is_ an existing ref.

Cf. 358ddb62cfd0 (Add "git show-ref" builtin command, 2006-09-15)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]