From: Larry McVoy <lm@bitmover.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Larry McVoy <lm@bitmover.com>,
linux-kernel@vger.kernel.org, bitkeeper-users@bitmover.com
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Sun, 14 Dec 2003 15:44:23 -0800 [thread overview]
Message-ID: <20031214234423.GB15850@work.bitmover.com> (raw)
In-Reply-To: <2122.1071443103@kao2.melbourne.sgi.com>
On Mon, Dec 15, 2003 at 10:05:03AM +1100, Keith Owens wrote:
> On Sun, 14 Dec 2003 09:21:56 -0800,
> Larry McVoy <lm@bitmover.com> wrote:
> >I've prototyped an extension to BitKeeper that provides tarballs
> >and patches. ...
> >... You need to understand that this is all you get,
> >we're not going to extend this so you can do anything but track the most
> >recent sources accurately. No diffs. No getting anything but the most
> >recent version. No revision history.
>
> Do we get the changelogs from each BK check in? Without the
> changelogs, patches are going to be much less useful.
You already get those, use BK/Web. It's all there and always has been.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-12-14 23:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 17:21 RFC - tarball/patch server in BitKeeper Larry McVoy
2003-12-14 23:05 ` Keith Owens
2003-12-14 23:44 ` Larry McVoy [this message]
2003-12-15 0:25 ` Keith Owens
2003-12-15 3:47 ` Larry McVoy
2003-12-14 23:17 ` Tupshin Harper
2003-12-14 23:43 ` Larry McVoy
2003-12-15 0:19 ` Tupshin Harper
2003-12-15 3:46 ` Larry McVoy
2003-12-15 6:07 ` Tupshin Harper
2003-12-15 16:02 ` Larry McVoy
2003-12-15 19:52 ` Tupshin Harper
2003-12-15 6:31 ` Martin J. Bligh
2003-12-15 12:11 ` Sergey Vlasov
2003-12-15 13:27 ` Ben Collins
2003-12-15 16:24 ` Sergey Vlasov
2003-12-15 16:32 ` Larry McVoy
2003-12-15 18:31 ` Andrea Arcangeli
2003-12-15 18:58 ` Larry McVoy
2003-12-15 19:40 ` Andrea Arcangeli
2003-12-15 21:44 ` Larry McVoy
2003-12-15 22:02 ` Andrea Arcangeli
2003-12-15 22:14 ` Larry McVoy
2003-12-15 22:44 ` Tupshin Harper
2003-12-15 23:13 ` Andrea Arcangeli
2003-12-15 22:36 ` Tupshin Harper
2003-12-15 22:46 ` Larry McVoy
2003-12-15 23:08 ` Tupshin Harper
2003-12-17 4:47 ` Matthew D. Pitts
2003-12-15 15:42 ` Larry McVoy
2003-12-15 15:55 ` Martin J. Bligh
2003-12-15 23:18 ` Chris Frey
2003-12-21 20:02 ` Pavel Machek
2003-12-21 20:46 ` John Bradford
2003-12-24 1:49 ` 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=20031214234423.GB15850@work.bitmover.com \
--to=lm@bitmover.com \
--cc=bitkeeper-users@bitmover.com \
--cc=kaos@ocs.com.au \
--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