Re: [PATCH 1/2] notes get-ref: --expand expands the output notes ref.

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

 



Johan Herland <johan@xxxxxxxxxxx> writes:

> On Wed, Sep 5, 2012 at 2:52 PM, W. Trevor King <wking@xxxxxxxxxx> wrote:
>> From: "W. Trevor King" <wking@xxxxxxxxxx>
>>
>> Useful for debugging refs that don't seem to be expanding correctly.
>>
>> Signed-off-by: W. Trevor King <wking@xxxxxxxxxx>
>
> Acked-by: Johan Herland <johan@xxxxxxxxxxx>

Really?  Would "git log --expand master" be useful?

I'd have to say that a DWIM that the user needs to diagnose with
such a "feature" is a total failure.  Can't we fix that root cause
instead?

That is, for a name, e.g. "refs/remotes/origin/notes/commit" (the
original example in [PATCH 0/2]) or "commit" (the usual):

 - If it is already a ref, just use that (e.g. use that stuff in the
   refs/remotes/ hierarchy); or

 - If it is not, prefix refs/notes/ to it.

or something?
--
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]