From: Stratos Psomadakis <psomas@ece.ntua.gr>
To: Matt Mackall <mpm@selenic.com>
Cc: 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 23:32:25 +0300 [thread overview]
Message-ID: <4DEE8AD9.3050508@ece.ntua.gr> (raw)
In-Reply-To: <1307477435.4204.968.camel@calx>
On 06/07/2011 11:10 PM, Matt Mackall wrote:
> On Tue, 2011-06-07 at 22:48 +0300, Stratos Psomadakis wrote:
>> On 06/07/2011 03:53 PM, Matt Mackall wrote:
>>> On Tue, 2011-06-07 at 08:40 +0100, Frank Kingswood wrote:
>>>> Hi!
>>>>
>>>> With Linux 3.0 approaching rapidly, is the ketchup script known to work?
>>>> It has this tempting <ver> parameter but I've always passed in "2.6" there.
>>> It's on its third maintainer now and I've already forgotten the name of
>>> the new guy.
>> It's me :P
>>
>> I uploaded the ketchup code at github, and added some code to handle 3.x
>> versions, but I've not tested it very much, so it's still in a separate
>> branch. [1]
>> You can check it out/test it, if you want. If it works without problems,
>> when linux-3.0 gets released, I'll tag a new version of ketchup and
>> notify distro maintainers to upgrade their packages.
> I took a brief glance at your changes. You'll probably want to teach it
> that 2.6.39++ == 3.0 so that people can seamlessly move back and forth
> between the two ranges. This wasn't something that made sense across the
> 2.4/2.6 transition.
>
> Oh, wait, maybe I've spotted the code for this.
>
> Thinking ahead just a bit, it'd be nice if we could just declare in
> advance that 3.9++ == 4.0. If we're going to bump the major number at
> arbitrary points, that's the most obvious one. It's approximately 3
> years out at the current rate which seems like a good pace. Then tools
> like ketchup and other tools that handle these version numbers could
> just do all this once.
>
> Linus?
Yeap, that would be nice, indeed. Otherwise, ketchup code (and other
tools probably) will get uglier and uglier as major numbers advance, and
I made it look ugly already (although this is probably 'thinking way
into the future').
--
Stratos Psomadakis
<psomas@ece.ntua.gr>
next prev parent reply other threads:[~2011-06-07 20:33 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 [this message]
2011-06-07 20:46 ` Matt Mackall
2011-06-07 20:50 ` david
2011-06-07 20:59 ` Matt Mackall
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=4DEE8AD9.3050508@ece.ntua.gr \
--to=psomas@ece.ntua.gr \
--cc=frank@kingswood-consulting.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--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