From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
git@vger.kernel.org, Johan Herland <johan@herland.net>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: Idea: "git format-patch" should get more information out of git
Date: Tue, 30 Aug 2011 17:41:01 +0200 [thread overview]
Message-ID: <4E5D048D.4010902@drmicha.warpmail.net> (raw)
In-Reply-To: <20110830152217.GA13022@sigill.intra.peff.net>
Jeff King venit, vidit, dixit 30.08.2011 17:22:
> On Tue, Aug 30, 2011 at 02:21:13PM +0200, Michael J Gruber wrote:
...
>> Anyways, notes survive rebase etc.
>
> You still have to manually configure:
>
> git config notes.rewriteRef refs/notes/commits
>
> Perhaps that is something that should be changed.
Right, I've done that quite a while ago and forgot.
>> and at format-patch time you can decide whether you want to include
>> them or not (with my patch).
>
> Yeah. Don't get me wrong, I think putting "---" notes into git-notes is
> way more flexible. It's just that it's also more complex, and
> unnecessarily so for many use cases.
>
> We have some patches to hide that complexity, but I was at one point
> wondering if all of the complexity was worthwhile. But as I mentioned
> above, if you want to build anything more complex than a pure-patch
> workflow, the simple solution breaks down. So it probably is worth
> pursuing.
Reminds me of the ref namespace restructuring which could help sharing
notes... Oh, lots to do before git 3.0!
Michael
next prev parent reply other threads:[~2011-08-30 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 5:12 Idea: "git format-patch" should get more information out of git Michael Haggerty
2011-08-27 18:46 ` Junio C Hamano
2011-08-27 20:35 ` Michael J Gruber
2011-08-28 6:21 ` Michael Haggerty
2011-08-28 6:34 ` Junio C Hamano
2011-08-29 18:55 ` Jeff King
2011-08-30 12:21 ` Michael J Gruber
2011-08-30 15:22 ` Jeff King
2011-08-30 15:41 ` Michael J Gruber [this message]
2011-08-30 17:39 ` Johan Herland
2011-09-01 4:32 ` Michael Haggerty
2011-09-01 6:44 ` Michael J Gruber
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=4E5D048D.4010902@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
/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).