From: "David S. Miller" <davem@redhat.com>
To: Dave Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: maintaining DRM and using bitkeeper..
Date: Thu, 26 Aug 2004 17:59:37 -0700 [thread overview]
Message-ID: <20040826175937.1da66716.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408270043170.25111@skynet>
On Fri, 27 Aug 2004 00:57:56 +0100 (IST)
Dave Airlie <airlied@linux.ie> wrote:
> it takes most of an evening to clone a tree to my
> machine at home
Why?
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 :-)
next prev parent 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 [this message]
2004-08-27 1:11 ` Dave Airlie
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=20040826175937.1da66716.davem@redhat.com \
--to=davem@redhat.com \
--cc=airlied@linux.ie \
--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®