Messages in this thread | | | Date | Thu, 03 Mar 2005 14:48:28 -0500 | From | Jeff Garzik <> | Subject | Re: [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec |
| |
Greg KH wrote:
Two procedural suggestions...
> Ok, I've fixed up the patch and applied it to a local tree that I've set > up to catch these things (it will live at > bk://kernel.bkbits.net:gregkh/linux-2.6.11.y until Chris Wright and I > set up how we are going to handle all of this.)
My suggestion would be one of two alternatives:
1) At each release, Linus clones linux.bkbits.net/linux-2.6 to linux.bkbits.net/linux-2.6.11
and gives the "release team" access to push to linux-2.6.11 repo.
2) Create linux-release.bkbits.net, and some non-Linus person clones linux-2.6 at release time to linux-2.6.11.
This accomplishes two [minor] goals: a) the tree lives at bkbits.net, as has a name associated with the goal of the project
b) The repo has the _exact_ name of the kernel release. None of this "linux-2.6.11.y" stuff. Just "linux-2.6.11". Anything else violates the Principle of Least Surprise.
> Feel free to start pointing stuff like this at me and chris (we'll also > be setting up an alias for it.)
I was wondering if it would be possible to setup a list on vger that is public, but read-only to everyone but the $sucker team.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |