All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
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: Sun, 17 Mar 2002 03:15:27 +0100	[thread overview]
Message-ID: <20020317031527.A31674@devcon.net> (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:
> 
> So far I have found two ways to get from 1.157 to 1.158.  One is to pull from 
> the parent and then undo down to 1.158.  The only other way that has been 
> suggested to me is to pull 1.158 in parallel and then import the patch there.

If you have a clone of the full master 2.5 repository somewhere on
your harddisk, you can go just there and do a

% bk send -r1.158 - | bk receive /your/uml/repository

After that change to your uml repository and do a

% bk resolve

to apply the 1.158 changeset to your uml repository (if you give a
"-a" option to bk receive, bk resolve will be run automatically).

Andreas
-- 
       Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
     ---------------------------------------------------------
         +49 521 1365800 - af@devcon.net - www.devcon.net

  reply	other threads:[~2002-03-17  2:16 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 [this message]
2002-03-17  2:49   ` Adam Keys
2002-03-17  2:57     ` Adam Keys
2002-03-17  4:27 ` Larry McVoy

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=20020317031527.A31674@devcon.net \
    --to=aferber@techfak.uni-bielefeld.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.