Wolfram Sang wrote:
> On Sun, Jan 17, 2010 at 03:29:35PM +0100, Wolfgang Grandegger wrote:
>> Hello,
>>
>> as promised, I composed and committed a little README on how to get your
>> Socket-CAN changes into the Linux kernel or BerliOS repo. See:
>>
>> http://svn.berlios.de/svnroot/repos/socketcan/trunk/README.submitting-patches
>>
>> Any comment, feedback, correction or improvement is welcome. For your
>> convenience, I have attached the file below:
>>
>> Wolfgang.
>>
>>
>> How to get your Socket-CAN changes into the Linux kernel or BerliOS repo
>> ========================================================================
>>
>> The Socket-CAN repository at BerliOS [1] allows to build *out-of-tree*
>> Socket-CAN kernel modules and is mainly useful for old kernel versions
>> and development. Currently it is based on Subversion but we want to
>> switch to GIT sooner or later. We try to keep the BerliOS repo in sync
>> with the kernel by backporting patches from the kernel and vice versa.
>>
>> If your changes are already mature in terms of functionality and code
>> quality, you may want to get them immetiately into the mainline kernel.
> 
> immediately
> 
>> If you feel that's not already the case and some more discussion and
>> feedback is required, it's useful to prepare and publish a patch for the
>> BerliOS repo first. Also the requirements for acceptance are not that
>> strict than for kernel inclusion. If kernel inclusion is your primary
>> goal, it makes sense to start preparing patches for the kernel
>> straightaway. An eventual backport to the BerliOS repo is usually quite
>> simply and does not require a full review, reducing at the same time the
> 
> /simply/simple

Both fixed.

> 
>> maintainers workload.
>>
>> Patches for kernel inclusion:
>> ----------------------------
>>
>> For kernel inclusion you need to prepare patches against David Millers
>> "net-next-2.6" GIT tree, which you can get as shown below:
>>
>>   $ git clone \
>>     git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
> 
> I think the 80 columns-rule is really inconvenient here.

Well, the "\" is not that bad.

Wolfgang.
_______________________________________________
Socketcan-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-users

Reply via email to