Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Jim Freeman <jfree@sovereign.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: sync plea
Date: Wed, 21 Feb 2001 16:04:18 +0100	[thread overview]
Message-ID: <20010221160418.A21995@bacchus.dhis.org> (raw)
In-Reply-To: <20010221060711.A26654@sovereign.org>; from jfree@sovereign.org on Wed, Feb 21, 2001 at 06:07:11AM -0700

On Wed, Feb 21, 2001 at 06:07:11AM -0700, Jim Freeman wrote:

> I have a farm of MIPS, PPC, and IA32 machines that I need to
> keep running from a common current source tree.
> 
> The recent mips update into 2.4.2pre2 (thankyouthankyouthankyou...)
> has helped in this task, but the diff between any 2.4.2pre[n>=2] or
> 2.4.1-ac[n>=9] tree vs the MIPS cvs tree is still huge, and painful
> to cull through to wind up with a sane mips patch (should be fairly
> small since the update into 2.4.2pre2) against a 2.4.*{pre*|-ac*} tree.
> 
> A sync of mips cvs to any 2.4.1{pre*|-ac*} kernel post 2.4.2pre2
> would be of great use, but I don't know how much pain that entails
> for the maintainers.
> 
> In lieu of that, can anyone clue me in to newbie tricks (CVS or
> otherwise) for syncing 2 trees less painfully than culling diffs?

Imagine, that's what we do on a daily base.  The most easy receipe to make
diffs less painfull is half a gig of RAM which brings time for diffing
two kernel trees down to ~ 2s on an Origin or decent PC.

Unfortunately Linus dropped piles of additional patches I sent to him.
That's the standard way this works, so just wait ...

  Ralf

  reply	other threads:[~2001-02-21 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21 13:07 sync plea Jim Freeman
2001-02-21 15:04 ` Ralf Baechle [this message]
2001-02-22  6:48   ` Jim Freeman

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=20010221160418.A21995@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=jfree@sovereign.org \
    --cc=linux-mips@oss.sgi.com \
    /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