On Fri, Sep 20, 2013 at 12:34 PM, Jeff King <peff@xxxxxxxx> wrote: > On Fri, Sep 20, 2013 at 07:38:17AM +0200, Francis Moreau wrote: > >> I'm using notes in my project. I'm wondering if it's possible to save >> the state of the notes when I'm releasing/tagging a new version of my >> project so I can restore the saved notes state if I checkout back the >> old release. >> >> Therefore I would be able to inspect notes (which may have been >> removed or modified after the release) as they were when the release >> happened. > > The notes are stored as git trees, so you can point a "tag" ref at a > particular state, just as you would with a normal branch. The "git tag" > command expects to create refs under "refs/tags", whereas "git notes" > expects to find notes under "refs/notes". The simplest thing is to just > use "git update-ref" rather than "git tag" to create the pointer. Like: > > $ git update-ref refs/notes/v1.0 refs/notes/commits > > and then you can always view the v1.0 notes as: > > $ git --notes=v1.0 log > > You can even set the notes.displayRef config to always show v1.0 notes > when they are available for a commit. Though if they are a subset of the > current notes, you would expect to see duplicates. Depending on what you > are storing in your notes, you may want to clean out your notes tree > after the release. Thank you Jeff, that's what I was needing. -- Francis -- 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