git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Spiers <git@adamspiers.org>
To: git mailing list <git@vger.kernel.org>
Subject: git-rnotes: git-notes wrapper for sharing notes between repositories
Date: Mon, 29 Apr 2013 14:32:05 +0100	[thread overview]
Message-ID: <20130429133205.GA4672@pacific.linksys.moosehall> (raw)
In-Reply-To: <20130427132118.GA25295@pacific.linksys.moosehall>

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.

  reply	other threads:[~2013-04-29 13:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27 13:21 git-icing: sugary wrapper around git-cherry Adam Spiers
2013-04-29 13:32 ` Adam Spiers [this message]
2013-04-29 16:39   ` improvements to checks for core.notesRef / GIT_NOTES_REF / --ref Adam Spiers
2013-04-29 17:13     ` Junio C Hamano
2013-04-29 21:40       ` Adam Spiers
2013-04-30  0:32         ` Johan Herland
2013-04-30  0:40           ` Adam Spiers
2013-09-21 17:25   ` tools for making upstreaming / backporting easier in git Adam Spiers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130429133205.GA4672@pacific.linksys.moosehall \
    --to=git@adamspiers.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).