Re: contributing to the kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jan Hudec <bulb@xxxxxx> writes:

> On Wed, Oct 13, 2004 at 15:01:26 +0500, Zeeshan Ali wrote:
...
>>    Furthermore, normally to contribute to a project, one need to get
>> the latest (cvs/svn/etc) version of the project, hack on it and then
>> either commit their changes (IF they have the write access) or submit
>> the patch to the devel list. How things go in the kernel world? Do i
>> need to have an up2date copy of the kernel all the time to contribute
>> to it?
>
> Much kernel development is done simply on the most recent released
> (including the -pre and -rc versions). However kernel is in
> a revision-control-system now. It uses bitkeeper. You should be able to
> create your own branch in bitkeeper, work on it and then tell
> appropriate maintainer to merge it. There is introduction to bitkeeper
> in Documentation/BK-usage. There are also some scripts there, that you
> want to use if you use bitkeeper.

Also see the docs in Documentation like SubmittingPatches.

-- 
  Ed L Cashin <ecashin@xxxxxxxxxx>


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux