From: Larry McVoy <lm@bitmover.com>
To: Andre Tomt <andre@tomt.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bkbits.net web UI oddities after last crash
Date: Wed, 25 Jun 2003 08:46:02 -0700 [thread overview]
Message-ID: <20030625154602.GA25213@work.bitmover.com> (raw)
In-Reply-To: <1056475651.7646.128.camel@slurv.ws.pasop.tomt.net>
On Tue, Jun 24, 2003 at 07:27:31PM +0200, Andre Tomt wrote:
> Hi
>
> I noticed some rather strange behavior from
> http://linux.bkbits.net:8080/linux-2.4
I put up a new release that used MD5 based names for revision numbers rather
than the revision numbers (sort of like naming a file by inode number)
because the revision numbers shift around on you. It has bugs. Once we
work out the bugs the plus is that you'll be able to post a URL and it
will always get people to the same data which is not true today.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-06-25 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 17:27 bkbits.net web UI oddities after last crash Andre Tomt
2003-06-25 15:46 ` Larry McVoy [this message]
2003-06-25 16:06 ` Sam Ravnborg
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=20030625154602.GA25213@work.bitmover.com \
--to=lm@bitmover.com \
--cc=andre@tomt.net \
--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