git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: Michael J Gruber <drmicha@warpmail.net>,
	Jeff King <peff@peff.net>, Eric Blake <eblake@redhat.com>,
	Thomas Rast <trast@student.ethz.ch>
Subject: Re: git format-patch should honor notes
Date: Wed, 8 Dec 2010 11:12:11 +0100	[thread overview]
Message-ID: <201012081112.12112.johan@herland.net> (raw)
In-Reply-To: <4CFF3FE4.4080104@warpmail.net>

On Wednesday 08 December 2010, Michael J Gruber wrote:
> Also, in order to be really useful, I would need a place to store the
> cover letter also. I was experimenting a while back with a design for
> annotating branchnames which "basically" worked but haven't had time
> to really implement it. If I remember correctly, I had to set up some
> "bogus" refs to keep my notes from being garbage collected and was
> still figuring out the best place to put them. I'll dig it up when I
> have time to.

I believe the last time the issue of adding notes to branch names was 
discussed, the consensus was that rather than using notes, they could 
be stored using a custom entry in the config file, e.g.

  git config branch.mybranch.description "Description of mybranch"

I might have misremembered this, though.


...Johan

-- 
Johan Herland, <johan@herland.net>
www.herland.net

  reply	other threads:[~2010-12-08 10:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 21:53 git format-patch should honor notes Eric Blake
2010-12-07 22:10 ` Junio C Hamano
2010-12-07 22:11 ` Jeff King
2010-12-08  8:20   ` Michael J Gruber
2010-12-08 10:12     ` Johan Herland [this message]
2010-12-08 10:24       ` Michael J Gruber
2010-12-08 10:50         ` Johan Herland
2010-12-08 11:15   ` Thomas Rast

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=201012081112.12112.johan@herland.net \
    --to=johan@herland.net \
    --cc=drmicha@warpmail.net \
    --cc=eblake@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=trast@student.ethz.ch \
    /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).