linux-mips
[Top] [All Lists]

Re: How to keep uptodate a mips-linux port

To: moreau francis <francis_moreau2000@yahoo.fr>
Subject: Re: How to keep uptodate a mips-linux port
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Date: Fri, 1 Apr 2005 09:37:42 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <20050401073405.46077.qmail@web25102.mail.ukl.yahoo.com>
Mail-followup-to: moreau francis <francis_moreau2000@yahoo.fr>, linux-mips@linux-mips.org
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050401073405.46077.qmail@web25102.mail.ukl.yahoo.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.6+20040907i
On Fri, 2005-04-01 09:34:05 +0200, moreau francis <francis_moreau2000@yahoo.fr>
wrote in message <20050401073405.46077.qmail@web25102.mail.ukl.yahoo.com>:

> Now, let say I would like to update my customized
> "linux-2.6.10-rc2-mips" to "Linux 2.6.11-mips".
> What is the best approach ?

The best approach is to cleanly break out all your changes into
semantical patches and submit them to the prople who care about the
individual files. The MIPS-specific patches go to this list.

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

Attachment: signature.asc
Description: Digital signature

<Prev in Thread] Current Thread [Next in Thread>