mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@linux.ie>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: maintaining DRM and using bitkeeper..
Date: Fri, 27 Aug 2004 02:11:32 +0100 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0408270209350.25111@skynet> (raw)
In-Reply-To: <20040826175937.1da66716.davem@redhat.com>


> Why?

Thanks Dave, that sorts out the I'm stupid and don't know how to use
bitkeeper issue :-), I'm still not in the bk paradigm...

I'll give it a blast this evening...

Dave.

>
> You should always have a current vanilla linus-2.6 BK tree
> locally, and just pull into it occaisionally.  Then when
> you want to do work just clone it using links:
>
> 	bk clone -l linus-2.6 drm-2.6
>
> and fire away. This is the fastest way.
>
> If you're going:
>
> 	bk clone bk://linux.bkbits.net/linux-2.5 drm-2.6
>
> then no wonder it takes all evening :-)
>
> When I rebase I just go:
>
> 	cd linus-2.6
> 	bk pull
> 	cd ..
> 	mv tree treework
> 	bk clone -l linus-2.6 tree
> 	cd tree
> 	bk pull ../treework
>
> and that takes less than 10 minutes even on my super slow
> UltraSPARC machines :-)
>

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person


  reply	other threads:[~2004-08-27  1:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 23:57 Dave Airlie
2004-08-27  0:59 ` David S. Miller
2004-08-27  1:11   ` Dave Airlie [this message]
2004-08-27 17:38 ` Sam Ravnborg
2004-08-27 23:54   ` Dave Airlie
2004-08-28  0:09     ` David S. Miller

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=Pine.LNX.4.58.0408270209350.25111@skynet \
    --to=airlied@linux.ie \
    --cc=davem@redhat.com \
    --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

all inboxes | Powered by JetHome®