linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <roland@purestorage.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.3-rc2
Date: Thu, 2 Feb 2012 13:05:07 -0800	[thread overview]
Message-ID: <CAL1RGDWLM58+vBPEd-JKLN+MNHuX4JRme9GocsVCQsuxNU7R8w@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFye5iedspjus4YLi+r77Xq74bCq+MqU0HrTmDC5Dveivg@mail.gmail.com>

On Tue, Jan 31, 2012 at 1:59 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> One thing that has happened is that I've liked seeing the merge
> message things that have come in through signed tags so much that I've
> decided to try to write more explanations even for the merges that
> don't get that kind of love from their subsystem maintainers. Some
> subsystem maintainers (David with networking is a good example) have
> tended to write nice good explanations in their pull requests, and
> I've started to try to make those kinds of things part of my merge
> messages.

I know you're rarely shy about giving feedback but I'm curious if we're
far enough along in this signed tag pulling stuff for you to have thoughts
about best practices for the tag contents.  For example if you look at
my recent 18d3e0d75079 is there anything you'd rather have different
(although of course that was a very boring tag with no controversial
contents and no conflicts)?  Any naming conventions for tags?  Anything
else you want an excuse to pontificate about?

Thanks,
 - R.

  parent reply	other threads:[~2012-02-02 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 21:59 Linux 3.3-rc2 Linus Torvalds
2012-02-01 17:56 ` Nick Bowler
2012-02-02  3:35   ` Wu Fengguang
2012-04-02 15:56     ` Nick Bowler
2012-02-02 21:05 ` Roland Dreier [this message]
2012-02-03 18:31   ` Linus Torvalds
     [not found] <20120201150015.EBB2413A4D6@koiott.cyber.ee>
2012-02-01 15:16 ` Meelis Roos

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=CAL1RGDWLM58+vBPEd-JKLN+MNHuX4JRme9GocsVCQsuxNU7R8w@mail.gmail.com \
    --to=roland@purestorage.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).