From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: moreau francis <francis_moreau2000@yahoo.fr>
Cc: linux-mips@linux-mips.org
Subject: Re: How to keep uptodate a mips-linux port
Date: Fri, 1 Apr 2005 09:37:42 +0200 [thread overview]
Message-ID: <20050401073742.GO21175@lug-owl.de> (raw)
In-Reply-To: <20050401073405.46077.qmail@web25102.mail.ukl.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
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 #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-01 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 7:34 How to keep uptodate a mips-linux port moreau francis
2005-04-01 7:37 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-01 7:54 moreau francis
2005-04-01 8:31 ` Jan-Benedict Glaw
2005-04-04 11:51 ` Ralf Baechle
2005-04-04 7:37 moreau francis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050401073742.GO21175@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=francis_moreau2000@yahoo.fr \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox