From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] new bitkeeper tree for 2.5 linux/ia64 kernel
Date: Thu, 15 May 2003 21:32:10 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705849@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705780@msgid-missing>
Hi Bjorn,
>>>>> On Thu, 15 May 2003 10:37:06 -0600, Bjorn Helgaas <bjorn_helgaas@hp.com> said:
Bjorn> Here's what I did (on kernel.org, from memory):
Bjorn> mkdir ~/BK
Bjorn> (cd ~/BK && bk clone -q bk://lia64.bkbits.net/linux-ia64-2.4 linux-ia64-2.4)
Bjorn> mkdir -p ~/bkexport-cache/linux-ia64-2.4
Bjorn> mkdir -p /staging/helgaas/linux-ia64-2.4
Bjorn> mkdir -p /pub/linux/kernel/ports/ia64/v2.4/testing/cset
Bjorn> mkdir ~/bin
Bjorn> cp ~dwmw2/working/bkexport/bkexport.sh ~/bin/
Bjorn> cat <<-EOF > ~/bin/update-patch
Bjorn> #!/bin/sh
Bjorn> /bin/nice -n 12 /home/helgaas/bin/bkexport.sh /home/helgaas/BK/linux-ia64-2.4 /pub/linux/kernel/ports/ia64/v2.4/testing/cset /home/helgaas/bkexport-cache/linux-ia64-2.4 "" /staging/helgaas/linux-ia64-2.4
Bjorn> EOF
Bjorn> Then I just run ~/bin/update-patch by hand whenever I update
Bjorn> the BK tree. dwmw2 runs it periodically from cron for linux-2.4
Bjorn> and linux-2.5, but my updates are much less frequent, so I just
Bjorn> do it by hand.
Your memory is excellent. It worked without a hitch.
OK, for all you patch-heads:
http://www.kernel.org/pub/linux/kernel/ports/ia64/v2.5/testing/cset/
I added a cronjob to update it daily, but if it falls behind, I
probably won't notice. Just holler in that case.
Enjoy,
--david
prev parent reply other threads:[~2003-05-15 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 8:01 [Linux-ia64] new bitkeeper tree for 2.5 linux/ia64 kernel David Mosberger
2003-05-14 13:37 ` Jes Sorensen
2003-05-14 17:27 ` David Mosberger
2003-05-14 23:53 ` Keith Owens
2003-05-15 1:13 ` David Mosberger
2003-05-15 1:22 ` Keith Owens
2003-05-15 16:37 ` Bjorn Helgaas
2003-05-15 21:32 ` David Mosberger [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=marc-linux-ia64-105590723705849@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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