public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rolandd@cisco.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "Read my lips: no more merges" - aka Linux 2.6.14-rc1
Date: Tue, 13 Sep 2005 11:34:34 -0700	[thread overview]
Message-ID: <52d5nc7r5x.fsf@cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509122019560.3351@g5.osdl.org> (Linus Torvalds's message of "Mon, 12 Sep 2005 20:34:17 -0700 (PDT)")

Sorry for being dense, but can you say what "no more merges" means?

At the kernel summit we talked about no more git merges after the
initial devel period, and I'm wondering if that really is the policy.

As a concrete example, suppose I have a git tree with something like

 drivers/infiniband/hw/mthca/mthca_qp.c    |    2 +-
 drivers/infiniband/ulp/ipoib/ipoib_main.c |    2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

ie a couple of really small, simple fixes.  Emailing those to Andrew
as patches is fine by me, but it seems like it creates extra work for
Andrew and you.  So is email via Andrew what you want, or are "bugfix
only" git pulls OK?

Thanks,
  Roland

  parent reply	other threads:[~2005-09-13 18:34 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  3:34 "Read my lips: no more merges" - aka Linux 2.6.14-rc1 Linus Torvalds
2005-09-13  3:54 ` Alejandro Bonilla Beeche
2005-09-13  3:59   ` Keith Owens
2005-09-13  4:03     ` Alejandro Bonilla Beeche
2005-09-14  5:16     ` Alejandro Bonilla Beeche
2005-09-14 16:28       ` Jeff Garzik
2005-09-14 16:40         ` Alejandro Bonilla
2005-09-14 16:43       ` Linus Torvalds
2005-09-14 16:52         ` Alejandro Bonilla
2005-09-15  0:48       ` Alejandro Bonilla Beeche
2005-09-13 14:27   ` Linus Torvalds
2005-09-13  6:28 ` more fallout from ATI Xpress timer workaround (was: Linux 2.6.14-rc1) Cal Peake
2005-09-13 20:04   ` Jean Delvare
2005-09-13  6:33 ` "Read my lips: no more merges" - aka Linux 2.6.14-rc1 Sonny Rao
2005-09-13  7:04   ` Eric Dumazet
2005-09-15  4:06     ` David S. Miller
2005-09-15  4:22       ` Linus Torvalds
2005-09-15 20:13     ` Benjamin LaHaise
2005-09-15 20:32       ` Linus Torvalds
2005-09-15 21:08         ` Eric Dumazet
2005-09-15 20:41       ` Eric Dumazet
2005-09-13  7:34 ` Udo A. Steinberg
2005-09-13 10:40 ` Mathieu Fluhr
2005-09-13 11:15   ` Helge Hafting
2005-09-13 15:14   ` Linus Torvalds
2005-09-13 17:01   ` Mathieu Fluhr
2005-09-13 17:15     ` Linus Torvalds
2005-09-13 18:12       ` Mathieu Fluhr
2005-09-13 19:11         ` Linus Torvalds
2005-09-14  8:11           ` 2.6.13 brings buffer underruns when recording DVDs in 16x (was Re: "Read my lips: no more merges" - aka Linux 2.6.14-rc1) Mathieu Fluhr
2005-09-14  8:30             ` Andrew Morton
2005-09-14 10:32               ` Mathieu Fluhr
2005-09-14 10:58                 ` Andrew Morton
2005-09-14 11:12                   ` Alessandro Suardi
2005-09-14 15:04           ` "Read my lips: no more merges" - aka Linux 2.6.14-rc1 Bill Davidsen
2005-09-14 23:38   ` Redeeman
2005-09-13 18:34 ` Roland Dreier [this message]
2005-09-13 18:46   ` Linus Torvalds
2005-09-13 21:32     ` Horst von Brand
2005-09-13 19:57 ` Rafael J. Wysocki
2005-09-14 15:31 ` Bill Davidsen
2005-09-14 22:56   ` Matthew Garrett
2005-09-14 17:33 ` Bill Davidsen
2005-09-14 17:45   ` Bill Davidsen
2005-09-14 21:47 ` Henrik Persson
2005-09-14 23:20   ` Jesper Juhl
2005-09-16 19:51     ` Henrik Persson
2005-09-14 22:11 ` 2.6.14-rc1 on ATI hangs when executing _STA and _INI methods Peter Osterlund
2005-09-14 22:27   ` Linus Torvalds
2005-09-14 22:41     ` Peter Osterlund
2005-09-14 23:27 ` "Read my lips: no more merges" - aka Linux 2.6.14-rc1 Redeeman
2005-09-16  7:44 ` Tomasz Torcz
  -- strict thread matches above, loose matches on Subject: below --
2005-09-13  6:07 Voluspa
2005-09-14 17:04 Steve Lee

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=52d5nc7r5x.fsf@cisco.com \
    --to=rolandd@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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