From: "George Spelvin" <linux@horizon.com>
To: tglx@linutronix.de
Cc: arnd@arndb.de, lftan@altera.com, linux@horizon.com,
linux-kernel@vger.kernel.org,
torvalds@linux-foundation.horizon.com
Subject: Re: [GIT PULL] arch/nios2 for v3.19
Date: 9 Dec 2014 20:06:38 -0500 [thread overview]
Message-ID: <20141210010638.11895.qmail@ns.horizon.com> (raw)
Thomas Gleixner wrote:
> It's a bit sad that all the reviewed/acked-by information which has
> been sent throughout the review process is completely lost.
Well, in the case here where the ack comes in after the pull request,
obviously only the merger (Linus) can add it, but for older ones,
it seems like an obvious git feature request to have comments in the
annotated tag automatically copied to the merge commit message draft.
That way, the subsystem maintainer could write a branch summary, like
the [PATCH 0/n] summaries that are popular, and have it automatically
included in the history.
That just seems a more sensible place to put things than the pull
request e-mail.
(Preserving the signed annotated tag object itself is another
intriguing possibility, but not only is it a huge format change
to create a way for a commit to point to a tag, but I also don't
see how to avoid tag name collision problems.)
next reply other threads:[~2014-12-10 1:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 1:06 George Spelvin [this message]
2014-12-10 1:54 ` Theodore Ts'o
2014-12-10 3:05 ` George Spelvin
-- strict thread matches above, loose matches on Subject: below --
2014-12-09 8:36 Ley Foon Tan
2014-12-09 9:05 ` Arnd Bergmann
2014-12-09 20:52 ` Linus Torvalds
2014-12-09 22:49 ` Thomas Gleixner
2014-12-09 22:52 ` Linus Torvalds
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=20141210010638.11895.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=arnd@arndb.de \
--cc=lftan@altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.horizon.com \
/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
all inboxes | Powered by JetHome®