On Fri, Sep 18, 2009 at 02:54:12PM +0200, Wolfgang Grandegger wrote:
> Oliver Hartkopp wrote:
> > Wolfgang Grandegger wrote:
> >> Hello,
> >>
> >> there was a demand to move from svn to git from Marc and Sebastian. I
> >> also believe, that git would save some maintenance work, mainly because
> >> patches could be prepared and applied more easily to the trees used for
> >> development. Here are my ideas:
> >>
> >> - I would like to keep the out-of-tree code we have currently under SVN
> >> mainly because backward compatibility with older kernels is a really
> >> useful feature, not only for development but also for the real users.
> >> Maintaining a full git tree with that backward compatibility is much
> >> more work, I believe.
> >>
> >> - Move the SVN kernel/2.6/ tree to git, without the "old" drivers
> >> and plus strip-src.
> >>
> >> - Move the SVN can-utils to a separate git tree.
> >>
> >> - Abandon the SVN repository. We keep it, of course, also for support of
> >> 2.4, but we should not spend time for updates.
> >
> > Looks good.
>
> OK, but where should we host it. At kernel.org we have the problem of
> sharing write access to the GIT repository.
That's solveable - the x86 guys share the same tree.
> I'm also thinking that more
> people than you and me could have write access to maintain there driver(s).
In principle I think this is a bad idea.
If people are educated then committing patches is very simple
with "git am".
But that require that you are available to do so - which I from
personal experience know can be hard from time to time.
Sam
_______________________________________________
Socketcan-core mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-core
