From: Larry McVoy <lm@bitmover.com>
To: Adam Keys <akeys@post.cis.smu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK] Having a hard time updating by pre-patch
Date: Sat, 16 Mar 2002 20:27:03 -0800 [thread overview]
Message-ID: <20020316202703.J10086@work.bitmover.com> (raw)
In-Reply-To: <20020317005425.TVMQ1147.rwcrmhc52.attbi.com@there>
In-Reply-To: <20020317005425.TVMQ1147.rwcrmhc52.attbi.com@there>; from akeys@post.cis.smu.edu on Sat, Mar 16, 2002 at 06:54:00PM -0600
On Sat, Mar 16, 2002 at 06:54:00PM -0600, Adam Keys wrote:
> First let me describe my goal: I am trying to get UML working with the
> recent 2.5.x versions. Currently, the most recent UML patch for 2.5 is
> against 2.5.2-pre11.
>
> What I have done is clone'd http://linux.bkbits.net/linux-2.5 and then cloned
> that to a working repository. When I cloned I used -r1.157, which is the
> revision 2.5.2-pre11 was. I then apply the UML patch with bk import. My
> next step would be to go to rev 1.158 and make sure everything works.
> Provided everything is OK at that step, I would go to the next rev and repeat.
You can do that and it will take a while because you have to port forward
to each step. Why not just patch it in at 1.157 and then pull again to
pull it all the way forward?
Anyway, to do what you asked, here's what I'd do:
bk clone bk://linux.bkbits.net/linux-2.5
bk clone -lr1.157 linux-2.5 2.5.2-pre11
bk import -tpatch ....
bk clone -lr1.158 linux-2.5 next
bk pull
repeat
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
prev parent reply other threads:[~2002-03-17 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 0:54 [BK] Having a hard time updating by pre-patch Adam Keys
2002-03-17 2:15 ` Andreas Ferber
2002-03-17 2:49 ` Adam Keys
2002-03-17 2:57 ` Adam Keys
2002-03-17 4:27 ` Larry McVoy [this message]
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=20020316202703.J10086@work.bitmover.com \
--to=lm@bitmover.com \
--cc=akeys@post.cis.smu.edu \
--cc=linux-kernel@vger.kernel.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