On Sat, Apr 27, 2013 at 02:21:19PM +0100, Adam Spiers wrote: > Hi all, > > I just wrote a wrapper around git cherry which adds a splash of > colour, and facilitates exclusion of commits which should never be > upstreamed, by using a git-notes(1) namespace as a blacklist. > > It's just a quick hack and Ruby probably won't be to everyone's taste, > but I thought I'd mention it just in case it's of use / interest. > > https://github.com/aspiers/git-config/blob/master/bin/git-icing [snipped] I've just written another quick wrapper around 'git notes' which makes it less painless to share notes to and from remote repositories: https://github.com/aspiers/git-config/blob/master/bin/git-rnotes This makes sharing of notes as easy as: git rnotes $remote push git rnotes $remote fetch git rnotes $remote merge git rnotes $remote pull and was born from this discussion: http://stackoverflow.com/questions/12055303/merging-git-notes-when-there-are-merge-conflicts-in-them/ Once the Great Refs Namespace Debate is resolved[0], would this kind of UI would be a candidate for pushing into git-notes itself? Cheers, Adam [0] Maybe it has been already; I haven't been following closely. -- 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