mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org,
	len.brown@intel.com, jgarzik@pobox.com, tony.luck@intel.com,
	bcollins@debian.org, scjody@modernduck.com, dwmw2@infradead.org,
	rolandd@cisco.com, davej@codemonkey.org.uk, axboe@suse.de,
	shaggy@austin.ibm.com, sfrench@us.ibm.com
Subject: Re: merge status
Date: Thu, 10 Nov 2005 00:09:10 +0100	[thread overview]
Message-ID: <9a8748490511091509t226fcffcw70dd40e67a6d36ac@mail.gmail.com> (raw)
In-Reply-To: <20051109150141.0bcbf9e3.akpm@osdl.org>

On 11/10/05, Andrew Morton <akpm@osdl.org> wrote:
> James Bottomley <James.Bottomley@SteelEye.com> wrote:
> >
> > it's my contributors who drop me in it
> > by leaving their patch sets until you declare a kernel, dumping the
> > integration testing on me in whatever time window is left.
>
> Yes, I think I'm noticing an uptick in patches as soon as a kernel is
> released.
>
> It's a bit irritating, and is unexpected (here, at least).  I guess people
> like to hold onto their work for as long as possible so when they release
> it, it's in the best possible shape.
>
> I guess all we can do is to encourage people to merge up when it's working,
> not when it's time to merge it into mainline.
>
> One could just say "if I don't have it by the time 2.6.n is released, it
> goes into 2.6.n+2", but that's probably getting outside the realm of
> practicality.

I personally find that a nice flow is to just continuously push
patches to you to merge into -mm, then once the merge window opens you
usually push the stuff onto Linus and it'll make the next kernel.
Anything I submit after the merge window opens will just stay in -mm
and wait for the next merge window (or next+1 depending on the patch).

But then my stuff is usually quite simple, so I guess that doesn't
work for everyone, but for me at least it seems to work well.


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2005-11-09 23:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 21:35 Andrew Morton
2005-11-09 21:50 ` James Bottomley
2005-11-09 22:01   ` Linus Torvalds
2005-11-09 22:25     ` James Bottomley
2005-11-09 22:43       ` Linus Torvalds
2005-11-10  7:16         ` Jeff Garzik
2005-11-09 23:01       ` Andrew Morton
2005-11-09 23:09         ` Jesper Juhl [this message]
2005-11-09 23:58         ` Linus Torvalds
2005-11-10 13:28           ` Pavel Machek
2005-11-10  0:16         ` Con Kolivas
2005-11-10  0:25           ` Andrew Morton
2005-11-10  0:24         ` James Bottomley
2005-11-10  8:40         ` Jens Axboe
2005-11-10  8:56           ` Andrew Morton
2005-11-10  9:22             ` Jens Axboe
2005-11-10  9:30               ` Andrew Morton
2005-11-10  9:57                 ` git branches strategy (was Re: merge status) Jeff Garzik
2005-11-10 13:22                 ` merge status Dave Kleikamp
2005-11-10 13:26         ` Pavel Machek
2005-11-14 20:13         ` Bill Davidsen
2005-11-09 22:05 ` Roland Dreier
2005-11-09 22:12 ` Jody McIntyre
2005-11-09 22:18   ` Linus Torvalds
2005-11-09 22:23     ` Jody McIntyre
2005-11-09 22:45       ` Andrew Morton
2005-11-09 22:48       ` Linus Torvalds
2005-11-09 22:13 ` Anton Altaparmakov
2005-11-09 22:48   ` Andrew Morton
2005-11-09 22:58     ` Linus Torvalds
2005-11-09 22:41 ` Russell King
2005-11-10  7:20 ` Jeff Garzik
2005-11-10  8:41 ` Jens Axboe
     [not found] <OF4A6DAD74.A56B078E-ON872570B4.007A77CE-862570B4.007AC8BB@us.ibm.com>
2005-11-09 22:23 ` David Woodhouse
2005-11-09 22:54 Luck, Tony
2005-11-09 23:21 ` Andrew Morton
2005-11-10  7:38 Brown, Len
2005-11-10  7:47 ` Jeff Garzik
2005-11-10  8:19   ` Keith Owens
2005-11-10 17:17 Luck, Tony

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=9a8748490511091509t226fcffcw70dd40e67a6d36ac@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=bcollins@debian.org \
    --cc=davej@codemonkey.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rolandd@cisco.com \
    --cc=scjody@modernduck.com \
    --cc=sfrench@us.ibm.com \
    --cc=shaggy@austin.ibm.com \
    --cc=tony.luck@intel.com \
    --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

all inboxes | Powered by JetHome®