All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: david@lang.hm
Cc: Stratos Psomadakis <psomas@ece.ntua.gr>,
	linux-kernel@vger.kernel.org,
	Frank Kingswood <frank@kingswood-consulting.co.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: ketchup script and 3.0
Date: Tue, 07 Jun 2011 15:59:32 -0500	[thread overview]
Message-ID: <1307480372.4204.987.camel@calx> (raw)
In-Reply-To: <alpine.DEB.2.02.1106071349000.28905@asgard.lang.hm>

On Tue, 2011-06-07 at 13:50 -0700, david@lang.hm wrote:
> On Tue, 7 Jun 2011, Matt Mackall wrote:
> 
> > But my point is that if we have adhoc transitions, we will encounter the
> > "fix all the scripts and websites" pain at every transition. And tools
> > that are managed via distros and the like can literally take years to
> > get into the hands of users. It'd be nice if the copy of ketchup shipped
> > in <enterprise distro> just worked 3 years from now because 4.0 wasn't a
> > surprise.
> 
> if you special case 2.4->2.6, and make the default that 4.0 > 3.x, 5.0 > 
> 4.x, etc won't things 'just work' for the forseeable future?

No, because you sometimes want to know what 2.6.39++ is and what 3.0--
is.

For instance, to upgrade from 2.6.37.2 to 3.1.2, ketchup will want to
download, cache, and apply:

patch-2.6.37.2 (reversed!)
patch-2.6.38
patch-2.6.39
patch-3.0 ?? <- hopefully Linus will make a delta against 2.6.39!
patch-3.1
patch-3.1.2


-- 
Mathematics is the supreme nostalgia of our time.



  reply	other threads:[~2011-06-07 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  7:40 ketchup script and 3.0 Frank Kingswood
2011-06-07 12:53 ` Matt Mackall
2011-06-07 19:48   ` Stratos Psomadakis
2011-06-07 20:10     ` Matt Mackall
2011-06-07 20:32       ` Stratos Psomadakis
2011-06-07 20:46         ` Matt Mackall
2011-06-07 20:50           ` david
2011-06-07 20:59             ` Matt Mackall [this message]
2011-06-07 21:22               ` Stratos Psomadakis
2011-06-07 21:33                 ` Randy Dunlap
2011-06-11  6:02                   ` Américo Wang
2011-06-11 18:28                     ` Randy Dunlap
2011-06-08 16:21                 ` Florian Mickler

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=1307480372.4204.987.camel@calx \
    --to=mpm@selenic.com \
    --cc=david@lang.hm \
    --cc=frank@kingswood-consulting.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psomas@ece.ntua.gr \
    --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 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.