From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Cc: moreau francis <francis_moreau2000@yahoo.fr>
Subject: Re: How to keep uptodate a mips-linux port
Date: Fri, 1 Apr 2005 10:31:47 +0200 [thread overview]
Message-ID: <20050401083147.GQ21175@lug-owl.de> (raw)
In-Reply-To: <20050401075417.14596.qmail@web25106.mail.ukl.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]
On Fri, 2005-04-01 09:54:17 +0200, moreau francis <francis_moreau2000@yahoo.fr>
wrote in message <20050401075417.14596.qmail@web25106.mail.ukl.yahoo.com>:
> --- Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> > 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.
>
> I already tried this one, and it doens't seem to be
> the best one: I sent a patch a couple of months ago
> to the list, but I didn't get any answers...so I beg
> for Ralf to look at it on IRC, but he seems to have
> not time for it...So now I'm trying to find out a new
> approach....
Don't expect that sending a patch once always leads to it's prompt
acceptance. Pushing a patch *can* involve resending it multiple times,
over a long period of time. However, if a patch is in acceptable state
(that is, a half-way readable coding style, no superfluous debugging
output, ...), Ralf usually takes it quite fast.
> Futhermore, this solution can take several months
> before every patches have been submitted and accepted.
> During this while I'll need to be synchronised with
> CVS tree.
That isn't all that easy, especially with CVS and especially if you want
to keep patches in nicely separated changesets. With CVS, this
unfortunately involves some manual work, or clever scripting. But SCM
systems are a totally different topic. "quilt" may work for you, though.
(And yes, we all search for the solution[tm] to SCM. RFC 1925 comes to
mind, modified to "Easy to use, technically working and politically
correct: Pick any two (you can't have all three)." )
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 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 7:54 How to keep uptodate a mips-linux port moreau francis
2005-04-01 8:31 ` Jan-Benedict Glaw [this message]
2005-04-04 11:51 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 7:37 moreau francis
2005-04-01 7:34 moreau francis
2005-04-01 7:37 ` Jan-Benedict Glaw
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=20050401083147.GQ21175@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