Re: IA64 bitkeeper trees (again)

From: Ian Wienand <ianw_at_gelato.unsw.edu.au>
Date: 2004-08-25 16:28:35
On Mon, Aug 23, 2004 at 10:45:23AM -0700, Luck, Tony wrote:
> So what would you like the names of the symlinks to be?  I'm thinking
> of:
> 
>    linux-ia64-release-2.6.8.1 -> release-2.6
>    linux-ia64-test-2.6.8.1    -> test-2.6
>    linux-ia64-release-2.6.9   -> release-2.6.next
>    linux-ia64-test-2.6.9      -> test-2.6.next
> 
> but I'd be happy to entertain better suggstions.

Just an idea (and I may have misunderstood the process); why not name
the trees for the people they are going to, for example

test-2.6         -> linux-ia64-tony (the main IA64 development area)
test-2.6.next    -> linux-ia64-to-mm (patches waiting to go to -mm series)
release-2.6.next -> linux-ia64-to-linus (patches waiting to go to official kernel)

I'm still not sure where the other release tree fits in all of this
though. 

Under this my thinking was a developer sends (non-trivial) patch that
first goes into -tony where it makes the core ia64 developers happy,
gets moved into -mm where it is picked up and used by a wider
audience, eventually it gets put into -linus where it is moved into
the main kernel.  Smaller patches, like a compile fix or whatever, go
straight from -tony to -linus?

-i

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Received on Wed Aug 25 02:28:50 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:30 EST