From: Drew Northup <n1xim.email@gmail.com>
To: Peter Baumann <waste.manager@gmx.de>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: [OT] How to get the discussion details via notes
Date: Wed, 31 Oct 2012 08:29:33 -0400 [thread overview]
Message-ID: <CAM9Z-nnMF47p2aK+c4Nq=hYFfhYBsWqiKogW36Lre5o7vZonyw@mail.gmail.com> (raw)
In-Reply-To: <20121031095327.GB18557@m62s10.vlinux.de>
On Wed, Oct 31, 2012 at 5:53 AM, Peter Baumann <waste.manager@gmx.de> wrote:
> Dropping the Cc list, as this is off topic
>
> On Tue, Oct 30, 2012 at 11:05:29PM -0700, Jonathan Nieder wrote:
>> Sverre Rabbelier wrote:
>>
>> > Thanks for the thorough explanation. Perhaps some of that could make
>> > it's way into the commit message?
>>
>> It's fine with me if it doesn't, since the original commit message
>> covers the basics (current behavior and intent of the change) in its
>> first two paragraphs and anyone wanting more detail can use
>>
>> GIT_NOTES_REF=refs/remotes/charon/notes/full \
>> git show --show-notes <commit>
>>
>> to find more details.
>
> I seem to miss something here, but I don't get it how the notes ref
> becomes magically filled with the details of this discussion.
>
> Care to explain?
If I have an email thread I'd like to store alongside a commit I'll
put that into a note, but I usually don't push that kind of thing out
to a remote repo.
Does that help?
--
-Drew Northup
--------------------------------------------------------------
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
next prev parent reply other threads:[~2012-10-31 12:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 19:06 [PATCH v3 0/4] fast-export: general fixes Felipe Contreras
2012-10-30 19:06 ` [PATCH v3 1/4] fast-export: trivial cleanup Felipe Contreras
2012-10-30 19:06 ` [PATCH v3 2/4] fast-export: fix comparisson in tests Felipe Contreras
2012-10-30 19:06 ` [PATCH v3 3/4] fast-export: don't handle uninteresting refs Felipe Contreras
2012-10-30 19:06 ` [PATCH v3 4/4] fast-export: make sure refs are updated properly Felipe Contreras
2012-10-31 0:11 ` [PATCH v2 " Jonathan Nieder
2012-10-31 2:08 ` Felipe Contreras
2012-10-31 0:37 ` [PATCH v3 " Jonathan Nieder
2012-10-31 1:33 ` Sverre Rabbelier
2012-10-31 6:05 ` Jonathan Nieder
2012-10-31 9:53 ` [OT] How to get the discussion details via notes Peter Baumann
2012-10-31 12:29 ` Drew Northup [this message]
2012-10-31 14:10 ` Jeff King
2012-11-01 7:49 ` Peter Baumann
2012-10-31 2:13 ` [PATCH v3 4/4] fast-export: make sure refs are updated properly Felipe Contreras
2012-11-02 13:12 ` Jeff King
2012-11-02 14:55 ` Jonathan Nieder
2012-11-02 15:17 ` Johannes Schindelin
2012-11-02 15:19 ` Jeff King
2012-11-02 15:35 ` Felipe Contreras
2012-11-02 15:34 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM9Z-nnMF47p2aK+c4Nq=hYFfhYBsWqiKogW36Lre5o7vZonyw@mail.gmail.com' \
--to=n1xim.email@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=waste.manager@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).