All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Christoph Hellwig <hch@caldera.de>
Cc: lm@bitmover.com, hpa@kernel.org, linux-kernel@vger.kernel.org,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Linux 2.4 bitkeeper repository
Date: Fri, 22 Feb 2002 10:13:36 -0500	[thread overview]
Message-ID: <3C766020.FFC64A87@mandrakesoft.com> (raw)
In-Reply-To: <20020222160657.A7914@caldera.de>

Christoph Hellwig wrote:
> 
> Hi Larry & Peter,
> 
> 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?).

Stuff will start showing up on kernel.org presumeably when BitMover
works out how to do proper locking on a repository without giving
'other' and 'group' write permission.

I presume one can pretty easily set up a cron to do that... but I wonder
if it is ok with Marcelo?  If Marcelo has plans for that repository, we
ought not touch it probably.

In general, though, agreed :)

> 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.

As a temporary measure people can pull from
	http://gkernel.bkbits.net/marcelo-2.4

which is always up-to-date with the latest Marcelo pre-patch, and
contains nothing else.

	Jeff



-- 
Jeff Garzik      | "UNIX enhancements aren't."
Building 1024    |           -- says /usr/games/fortune
MandrakeSoft     |

  reply	other threads:[~2002-02-22 15:13 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 [this message]
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
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=3C766020.FFC64A87@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=hch@caldera.de \
    --cc=hpa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=marcelo@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.