From: Erik Andersen <andersen@codepoet.org>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BK/Web improvements (includes patch server)
Date: Mon, 15 Mar 2004 04:41:42 -0700 [thread overview]
Message-ID: <20040315114142.GA22039@codepoet.org> (raw)
In-Reply-To: <200403150616.i2F6Gu2Z030020@work.bitmover.com>
On Sun Mar 14, 2004 at 10:16:56PM -0800, Larry McVoy wrote:
> I've made a few changes to the BK/Web service on BK/Bits. There are some
> cosmetic changes but the substantial changes are as follows:
>
> - Traditional diff -Nur style patches served as text/plain. You can
> now wget your favorite patch.
Hey thats cool, I know I will use this often to slurp down
patches of interest.
<obligitory request for yet more stuff which is
almost certain to piss you off since you just
gave me yet-another-something-for-free>
I'm curious if you might consider adding a diff -Nur style
patch vs the last tagged version? I often go to:
http://www.kernel.org/pub/linux/kernel/v2.4/testing/cset/
and
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/
to obtain this sortof a patch, for example when I want to submit
a patch that is relevant to the current kernel tree, rather than
1000 patches behind. Sadly, these are often rather out of touch
with reality. Check out for example the 2.4 one, which has been
stuck since March 8th. :-(
Right now I can go to, for example:
http://linux.bkbits.net:8080/linux-2.4/ChangeSet@1.1326..?nav=index.html|tags
and see the list of patches, and thanks to your latest update, I
can now click on each patch one-by-one to suck down a diff. I
would sure love to be able to obtain the lot as cumulative patch
of everything after the last tagged version.
I do not know if that is something you might consider, if doing
so suites your business model, if doing so would make
unreasonable demands on your donated bandwidth, cpu power, etc,
etc, etc. But such a thing would certainly come in handy, if you
felt so inclined.
Of course, an alternative solution would be for someone to fix
the kernel.org testing/cset/ scripts to not get wedged...
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2004-03-15 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 6:16 BK/Web improvements (includes patch server) Larry McVoy
2004-03-15 11:41 ` Erik Andersen [this message]
2004-03-15 20:02 ` Andy Isaacson
2004-03-15 20:10 ` Jamie Lokier
2004-03-15 20:18 ` Andy Isaacson
2004-03-15 20:44 ` Jamie Lokier
2004-03-18 21:49 ` David Woodhouse
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=20040315114142.GA22039@codepoet.org \
--to=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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