On Fri, 29 Dec 2000, Sourav Sen wrote:
>
> Hi,
>
> This question may seem naive, but can anyone tell me if there is any
> structured way of writing patches?
1. get a base tree, e. g. 2.2.18, and unpack it into /usr/src
(rename your old /usr/src/linux first)
2. rename linux you got in 1. t
Jeff's descriprion is very informative, but his emphasis
is somewhat different from what I find difficult with patches.
First, for the life of me I was unable to remeber which
argument goes first (DaveM was mad every time). Second, I kept
forgetting to keep the base tree a diff against that instea
Sourav Sen <[EMAIL PROTECTED]> writes:
> Hi,
>
> This question may seem naive, but can anyone tell me if there is any
> structured way of writing patches?
>
> I mean suppose I want to implement some
> kernel mechanism, and I define my data structures etc. and made most of
> the code as loadabl
3 matches
Mail list logo