* Re: How to keep uptodate a mips-linux port
@ 2005-04-01 7:54 moreau francis
2005-04-01 8:31 ` Jan-Benedict Glaw
0 siblings, 1 reply; 6+ messages in thread
From: moreau francis @ 2005-04-01 7:54 UTC (permalink / raw)
To: Jan-Benedict Glaw; +Cc: linux-mips
--- 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....
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.
regards,
Francis
__________________________________________________________________
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: How to keep uptodate a mips-linux port
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
0 siblings, 1 reply; 6+ messages in thread
From: Jan-Benedict Glaw @ 2005-04-01 8:31 UTC (permalink / raw)
To: linux-mips; +Cc: moreau francis
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How to keep uptodate a mips-linux port
2005-04-01 8:31 ` Jan-Benedict Glaw
@ 2005-04-04 11:51 ` Ralf Baechle
0 siblings, 0 replies; 6+ messages in thread
From: Ralf Baechle @ 2005-04-04 11:51 UTC (permalink / raw)
To: linux-mips, moreau francis
On Fri, Apr 01, 2005 at 10:31:47AM +0200, Jan-Benedict Glaw wrote:
> > 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.
Unless he's on vacation and tries to be a happy man by avoiding email
software ;-)
> > 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.
I recommend Quilt which is availalble from Savannah. It's done a great
job for me in developping and maintaining a bunch of patches independant
of each other.
Ralf
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How to keep uptodate a mips-linux port
@ 2005-04-04 7:37 moreau francis
0 siblings, 0 replies; 6+ messages in thread
From: moreau francis @ 2005-04-04 7:37 UTC (permalink / raw)
To: Jan-Benedict Glaw, linux-mips; +Cc: moreau francis
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
^ permalink raw reply [flat|nested] 6+ messages in thread* How to keep uptodate a mips-linux port
@ 2005-04-01 7:34 moreau francis
2005-04-01 7:37 ` Jan-Benedict Glaw
0 siblings, 1 reply; 6+ messages in thread
From: moreau francis @ 2005-04-01 7:34 UTC (permalink / raw)
To: linux-mips
Hi,
I plan to keep uptodate a port that I realized during
last months. But I don't know how to proceed...
Explanation: I used "linux-2.6.10-rc2-mips" snapshot
as starting point. I did some minor changes on generic
files (files which are not part of mips branch) as
well as mips specific files and added specific board
files.
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 ?
Thanks for your advices
Francis
__________________________________________________________________
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2005-04-04 11:52 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
-- 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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox