On Wed, Feb 12, 2014 at 1:06 AM, Junio C Hamano <gits...@pobox.com> wrote:
> Johan Herland <jo...@herland.net> writes:
>> There is currently no way the "git notes" commands will allow you to
>> store the 3d7de37 commit object directly as a note. There is also
>> (AFAICS) no easy workaround (git fast-import could've been a
>> workaround if it did not already require the first N/notemodify
>> argument to be a blob object). The best alternative, off the top of my
>> head, would be to write your own program using the notes.h API to
>> manipulate the notes tree directly (or - suboptimally - use other
>> low-level Git operations to do the same).
> Even worse. I do not think such a non-blob object in the notes tree
> does not participate in the reachability at all, so you won't be
> able to fetch "refs/notes/whatever" and expect to get a useful
Any object type that is deemed reachable by reference from a regular
git tree object will also be usable (as far as reachability goes) in a
> I do not think storing the raw bits of commit object as a
> blob in the notes tree is useful behaviour, either. The command
> probably should refuse to get anything non-blob via that option.
Patch coming up...
> Perhaps the notes entry should just note the object name of whatever
> commit it wants to refer to in a *blob*?
Johan Herland, <jo...@herland.net>
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html