I'm playing around with git-notes and want to share some of my notes
with my co-workers. We have a central repository for our various topic
branches and want to track upstream inclusion in git-notes. So we have
to share our notes branch somehow.

The workflow I think makes sense here is (untested):

        ### hack hack, add notes bla blub
        ### -> nice topic branch with some notes

        git fetch serverrepo refs/notes/commits:refs/notes/servercommits
        git notes merge refs/notes/servercommits
        git rev-list origin/master.. | awk '{print $1 " " $1}' | git notes copy 
--to refs/notes/servercommits --stdin
        git push serverrepo refs/notes/servercommits:refs/notes/commits

Then maybe:

        git notes merge refs/notes/servercommits


The idea here is to only include notes in refs/notes/servercommits that
are relevant for my coworkers and not all intermediate notes that were
created during development or while working on other branches.

Does this make sense? Do you have better ideas or suggestions how to
improve the workflow?

The only problem now is that git notes copy doesn't take a --to
parameter. Maybe there is a volunteer to implement it? Then I'd
volunteer to test it :-)

Best regards

Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
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