Am 13.10.2011 11:10, schrieb Wolfgang Grandegger: > Hi Marc, > > On 10/13/2011 10:37 AM, Marc Kleine-Budde wrote: >> Hello, >> >> On 10/13/2011 09:13 AM, Wolfgang Grandegger wrote: >>> over night, while I was sleeping, the mailing list moved :-), let's go >>> ahead finding a new home for the can-utils, kernel-out-of-tree and maybe >>> libsocketcan... >> >> I think it's a good idea to import the berlios svn subtree containing >> the can-utils into the git repo on the new server. The git history looks >> better if we convert the svn usernames to a proper author field, e.g.: >> "John Developer <john.develo...@example.com>". > > Yep, as described also in "Importing from SVN" at > > http://savannah.gnu.org/maintenance/UsingGit > >> Urs, Oliver, Wolfgang and all other contributors, what's your preferred >> email? > > Wolfgang Grandegger <w...@grandegger.com> > >>From that description it also seems that we can push only to one git > repository per project. This again rises the question how to handle and > name the can-utils and can-kmods. I see the following possibilities: > > 1. *One* project named "socketcan" or "linux-can" for both. In the git > repo we could then store all socketcan related code in: > > can-utils/... The CAN Utils > can-lib/... Eventually A Socketcan library, might be > integrated into can-utils > kernel/... Out-of-tree kernel modules for 2.6 and 3.x > kernel-2.4/... Old kernel modules for 2.4 > > 2. *Two* different projects named "can-utils" and "can-kmod". > > Any preferences?
I prefer the second variant. Yegor _______________________________________________ Socketcan-core mailing list Socketcan-core@lists.berlios.de https://lists.berlios.de/mailman/listinfo/socketcan-core
