Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: moreau francis <francis_moreau2000@yahoo.fr>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>, linux-mips@linux-mips.org
Cc: moreau francis <francis_moreau2000@yahoo.fr>
Subject: Re: How to keep uptodate a mips-linux port
Date: Mon, 4 Apr 2005 09:37:18 +0200 (CEST)	[thread overview]
Message-ID: <20050404073718.12908.qmail@web25110.mail.ukl.yahoo.com> (raw)
In-Reply-To: 6667


Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> 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.

Ok, I'll retry.

> 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. 

Actually that's what I was looking for...

Cheers.

         Francis



	
	
		
___________________________________________________________________________________________________
Le nouveau Yahoo! Messenger est arrivé ! Découvrez toutes les nouveautés pour dialoguer instantanément avec vos amis. A télécharger gratuitement sur http://fr.messenger.yahoo.com 

             reply	other threads:[~2005-04-04  7:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04  7:37 moreau francis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-01  7:54 How to keep uptodate a mips-linux port moreau francis
2005-04-01  8:31 ` Jan-Benedict Glaw
2005-04-04 11:51   ` Ralf Baechle
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=20050404073718.12908.qmail@web25110.mail.ukl.yahoo.com \
    --to=francis_moreau2000@yahoo.fr \
    --cc=jbglaw@lug-owl.de \
    --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