On Sat, Mar 04, 2006 at 01:34:53AM -0500, Pavel Roskin wrote:
> Hello!
>
> I have finally found time to reconcile our CVS repository with the Linux
> kernel. The result is available in the "for_linus" branch. It would
> only compile for 2.6.16 prereleases. My plan is to submit changes for
> 2.6.17 once 2.6.16 is released.
Excellent. You might wish to consider submitting them to akpm for -mm
right now. That will give them a bit more testing there, and Andrew
will probably push them into mainline for you once 2.6.16 is released.
> I hope it's the last manual reconciliation, thanks to the progress in
> the versioning systems. In particular, git and StGIT have finally
> become useful and stable.
>
> I currently have two git repositories, one is for the kernel and the
> other is only for the driver. The driver git repository was converted
> from the CVS repository.
>
> Both repositories store all new patches as StGIT patches. StGIT is
> specifically designed to operate on patches. The last commits in the
> for_linus branch were actually exported from the driver git repository.
>
> The kernel repository has patches that will be sent to the kernel
> developers. I still need to do some work on splitting patches that will
> got to the kernel. Some of them are too large. But the important thing
> is that both repositories are in-sync, and any changes in one repository
> can be easily moved to the other.
>
> Now, the question is how to share this work with other developers and
> testers. There are some issues here.
>
> I don't have a place to host git repositories. I can continue to export
> to CVS from the Orinoco git repository. Unfortunately, CVS is quite bad
> at handling branches and commits made in a quick succession. I had to
> deal with both already, and I'm afraid we'll have to deal with it even
> more.
>
> Since SourceForge offers Subversion, I'm thinking of converting the
> repository to Subversion and moving it from Savannah to SourceForge.
> Another approach would be to use Arch on Savannah, but it would be a
> steep learning curve both for me and for testers. Finally, I could ask
> kernel developers to give a repository on kernel.org/git.
Introducing yet another SCM to the mix seems foolish. Plus for
easiest possible integration with the mainline kernel, git is the only
way to go. I think trying to find somewhere to host the git tree is
by far the better option. If you can't get something on kernel.org, I
might be able to host them on ozlabs.org
> As for the next release, I still need to port PCMCIA changes to older
> kernels, which is another big effort.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
|
| 
