On 10/13/2011 08:12 PM, Oliver Hartkopp wrote: > On 10/13/11 11:20, Marc Kleine-Budde wrote: > >> On 10/13/2011 11:10 AM, Wolfgang Grandegger wrote: > >>> 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". >> >> At least two repos, one for the userspace one for the kernel. Maybe even >> more then one userspace repo. > > > Yes. Having separated kernel-space and user-space repos looks good. > > If we have the possibility to have more than one repos as Martin pointed out > here > > http://git.savannah.gnu.org/cgit/freetype/ > > we could name them e.g. > > can/user.git > can/kernel.git > > while user.git contains directories 'utils', 'lib', 'samples', 'apps?' > and kernel.git contains directories 'linux-2.4' and 'linux'
I don't like user.git and kernel.git, because when you do a git clone, you have directories called "user" and "kernel". Especially "user" is too generic. Using git it makes IMHO no sense to have linux-2.4 and linux (>=2.6) next to each other in one repo. Either make it two repos or two heads. If you have linux-can.git containing the 2.6+ out-of-tree modules you can cherry pick fixes from the mainline kernel. > I'm not really sure about the naming though. Marc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
