On 23 October 2012 21:51, Jeff King <peff@xxxxxxxx> wrote: > On Tue, Oct 23, 2012 at 10:47:28PM +0200, Thomas Gleixner wrote: > >> I agree that this is a common issue. Acked-by/Reviewed-by mails come >> in after the fact that the patch has been committed to an immutable >> (i.e no-rebase mode) branch or if the change in question already hit >> Linus tree. >> >> Still it would be nice to have a recording of that in the git tree >> itself. >> >> Something like: "git --attach SHA1 <comment>" would be appreciated! > > It is spelled: > > git notes add -m <comment> SHA1 > > The resulting notes are stored in a separate revision-controlled branch > and can be pushed and pulled like regular refs. Note, though, that the > default refspecs do not yet include refs/notes, so you'd have to add > them manually. The workflows around notes are not very mature yet, so if > you start using them, feedback would be appreciated. What would be nice is that notes are pushed/pulled automatically with standard git push/fetch/pull commands. Usually git walks the DAG starting with the pulled commit or tag and following the parents. With notes, the reference is reversed, the note pointing to the commit and not the other way around. So handling this automatically in Git would be really useful. The other feature I'd like is that notes are automatically folded in the log during git rebase (maybe similar to the squash option). If you rebase, you lose all the notes (though this depends on the workflow, it may not be needed with published branches). -- Catalin -- 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