Junio C Hamano <gits...@pobox.com> writes:

> I actually think this "recording information about commits" is
> exactly the use-case notes were invented to address, and if it is
> found cumbersome to use, the reason why it is cumbersome needs to be
> discovered and use of notes needs to be improved.  Hooks and/or a
> wrapper around "git commit" to implement their custom workflow may
> be involved as part of the solution and "git notes" may need to
> learn a new trick or two along the way.
> I am not interested in hearing "let's add random crud to commit
> object header" before "let's improve notes so that it can be more
> smoothly used" is fully explored.

Oh, I forgot to say that I do not have anything against embedding
the extra info as part of the free-form "log message" text part of
the commit object like you have been suggesting.  If the information
can be cast in stone at the commit time, that would actually be
preferrable, as you do not have to worry about transferring notes
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

Reply via email to