All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, george@mvista.com,
	zippel@linux-m68k.org, ulrich.windl@rz.uni-regensburg.de,
	tglx@linutronix.de
Subject: Re: [PATCH 8/11] Time: i386 Conversion - part 4: ACPI PM variable renaming and config change.
Date: Wed, 4 Jan 2006 02:41:13 -0800	[thread overview]
Message-ID: <20060104024113.73fe4266.akpm@osdl.org> (raw)
In-Reply-To: <1136370805.3788.19.camel@leatherman>

john stultz <johnstul@us.ibm.com> wrote:
>
> > Anyway, I'll tenatively merge these patches into next -mm so they can get a
> > bit of testing.  Which causes a problem, because you don't then have a tree
> > against which to raise a new patch series.
> 
> I greatly appreciate the inclusion! I'm hoping a bit of time in -mm will
> shake out any remaining bugs. 
> 
> Although I'm not sure I understand what you mean about me not having a
> tree? Do you mean a public git tree? 
> 

Sorry.  I meant that once I've merged this series into -mm, you can no
longer generate a new patch series against -mm!  If I were to leave this
patch series out of next -mm, you'd have a clean tree to raise patches
against.

>
> > So perhaps it would be best if you were to
> > 
> > a) Tell me which patches to fold into which other patches to generate a
> >    series which compiles at every stage and
> > 
> > b) Send me a new set of changelogs for the resulting patch series.
> 
> I've got a set of chained git trees that store each patch, so its very
> easy to re-generate the changelog + patches after I've re-arranged them
> as you suggested.
> 
> Would a new patch-set to replace the current patchset be preferred here
> or do you just want the above?  

Replacement would be best.  If you can regenerate the diffs against
whatever tree you generated the last batch, that would work.

> Similarly, if we do run into bugs, would you prefer incremental fixup
> patches or cumulative replacement patches when a new release of the
> patchset is generated?

minimally-sized incremental fixes are preferred, please.

> I'm just getting back from vacation tonight, so I'll send whatever you
> prefer sometime tomorrow.

That would be good, thanks.


  reply	other threads:[~2006-01-04 10:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16  1:07 [PATCH 0/11] Time: Generic Timeofday Subsystem (v B14-mm) john stultz
2005-12-16  1:07 ` [PATCH 1/11] Time: Reduced NTP rework (part 1) john stultz
2005-12-16  1:07 ` [PATCH 2/11] Time: Reduced NTP Rework (part 2) john stultz
2005-12-16  1:07 ` [PATCH 3/11] Time: Clocksource Infrastructure john stultz
2005-12-16  1:07 ` [PATCH 4/11] Time: Generic Timekeeping Infrastructure john stultz
2005-12-16  1:07 ` [PATCH 5/11] Time: i386 Conversion - part 1: Move timer_pit.c to i8253.c john stultz
2005-12-16  1:07 ` [PATCH 6/11] Time: i386 Conversion - part 2: Move timer_tsc.c to tsc.c john stultz
2005-12-16  1:07 ` [PATCH 7/11] Time: i386 Conversion - part 3: Rework TSC Support john stultz
2005-12-16  1:08 ` [PATCH 8/11] Time: i386 Conversion - part 4: ACPI PM variable renaming and config change john stultz
2006-01-04  0:35   ` Andrew Morton
2006-01-04 10:33     ` john stultz
2006-01-04 10:41       ` Andrew Morton [this message]
2005-12-16  1:08 ` [PATCH 9/11] Time: i386 Conversion - part 5: Enable Generic Timekeeping john stultz
2005-12-16  1:08 ` [PATCH 10/11] Time: i386 Conversion - part 6: Remove Old Code john stultz
2005-12-16  1:08 ` [PATCH 11/11] Time: i386 Clocksource Drivers john stultz

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=20060104024113.73fe4266.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=george@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=ulrich.windl@rz.uni-regensburg.de \
    --cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.