From: Larry McVoy <lm@bitmover.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-kernel@vger.kernel.org, marcelo@conectiva.com.br,
lm@bitmover.com
Subject: Re: linux-2.4 bitkeeper repository not up to date
Date: Mon, 25 Mar 2002 08:55:34 -0800 [thread overview]
Message-ID: <20020325085534.K4755@work.bitmover.com> (raw)
In-Reply-To: <200203251544.g2PFiaV02011@localhost.localdomain> <22088.1017071834@redhat.com>
On Mon, Mar 25, 2002 at 03:57:14PM +0000, David Woodhouse wrote:
> James.Bottomley@HansenPartnership.com said:
> > The repository linux24.bkbits.net is only at 2.4.19-pre3; however, the
> > kernel test directory is at 2.4.19-pre4. I seem to remember that
> > when we had this problem with the 2.5 repository it was a scripting
> > issue.
>
> Use linux.bkbits.net/linux-2.4 instead.
>
> We should probably remove linux24.bkbits.net. Marcelo? Larry?
In general, we don't automatically clean out old repositories here though
I suspect that will have to change as usage levels rise. We are going to
start insisting that we get a valid email address when you create a project
on bkbits.net so we can send you mail to ask if you care about something
we want to clean up.
If you created stuff on bkbits.net that you no longer use/need, please log
in as your_proj.adm and do a rm_proj on it.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
prev parent reply other threads:[~2002-03-25 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 15:44 linux-2.4 bitkeeper repository not up to date James Bottomley
2002-03-25 15:57 ` David Woodhouse
2002-03-25 16:55 ` Larry McVoy [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=20020325085534.K4755@work.bitmover.com \
--to=lm@bitmover.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox