From: Tom Rini <trini@kernel.crashing.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Christoph Hellwig <hch@caldera.de>,
lm@bitmover.com, hpa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 bitkeeper repository
Date: Fri, 22 Feb 2002 12:37:23 -0700 [thread overview]
Message-ID: <20020222193723.GL719@opus.bloom.county> (raw)
In-Reply-To: <20020222160657.A7914@caldera.de> <Pine.LNX.4.33L.0202221625480.7820-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0202221625480.7820-100000@imladris.surriel.com>
On Fri, Feb 22, 2002 at 04:26:42PM -0300, Rik van Riel wrote:
> On Fri, 22 Feb 2002, Christoph Hellwig wrote:
>
> > the Linux 2.4 repository at linux.bkbbits.net is orphaned short after
> > it got created. Ist there any chance we could see continguous checkins
> > for it?
> >
> > I think it might be a good idea to get it automatically checked in once
> > Marcelo uploads a new (pre-) patch as part of the kernel.org
> > notification procedure (is this possible, Peter?).
> >
> > If there is no way to automate it I would volunteer to do the checkins,
> > but for that I'd need write permissions to the repository.
>
> I've got a script here which pretty much automates the
> checkins of incremental patches, it should be trivial
> for Peter to call that from his script that creates the
> incremental diffs.
If you have a pristine tree, adding incremental diffs is:
bk import -tpatch ../patch-2.4.X-preY-preZ . && bk tag v2.4.X-preZ
Which is what I do for the PPC's kernel.org-only tree(s).
Larry or Cort Dougan came up w/ a script ages ago to do it w/o
incrmenetal diffs and to make a backup as well.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-02-22 19:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 15:06 Linux 2.4 bitkeeper repository Christoph Hellwig
2002-02-22 15:13 ` Jeff Garzik
2002-02-22 15:26 ` DevilKin
2002-02-22 15:40 ` Jeff Garzik
2002-02-22 15:44 ` Stelian Pop
2002-02-22 16:36 ` Marcelo Tosatti
2002-02-22 18:42 ` Larry McVoy
2002-02-22 19:37 ` Rik van Riel
2002-02-22 19:45 ` Larry McVoy
2002-02-23 19:40 ` Linus Torvalds
2002-02-22 16:53 ` Larry McVoy
2002-02-22 19:26 ` Rik van Riel
2002-02-22 19:37 ` Tom Rini [this message]
2002-02-22 19:49 ` Rik van Riel
2002-02-23 0:35 ` Tom Rini
2002-02-23 1:32 ` Larry McVoy
2002-02-23 1:46 ` Davide Libenzi
2002-02-23 1:58 ` 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=20020222193723.GL719@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=hch@caldera.de \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=riel@conectiva.com.br \
/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.