In message <[EMAIL PROTECTED]> you wrote: > > Once there is a public tree with 2.6.20-rc1 + ipipe + -rc2, you cannot > simply turn that tree into 2.6.20-rc1 + -rc2 + ipipe. The order of > patches is practically frozen once published. In your private tree you > are, of course, free to do this and then extract some patch to post > upstream.
I'm not sure if it really makes sense to maintain this as a git repository - that would be OK if we wanted to provide a pre-patched tree to the public (which might be a good thing to have, btw.). As long as we're basicly trying to manage the patches in a way that integrates well with git we should do exactly that: manage the patches under git, i. e. use stgit (see http://www.procode.org/stgit/). Just my 0.02 <insert your favorite currency unit here> Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] The best things in life are for a fee. _______________________________________________ Adeos-main mailing list [email protected] https://mail.gna.org/listinfo/adeos-main
