From: "H. Peter Anvin" <hpa@transmeta.com>
To: Linus Torvalds <torvalds@transmeta.com>,
David Weinehall <tao@acc.umu.se>, Alan Cox <alan@redhat.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Prepatches and kernel.org incdiff robot
Date: Tue, 04 Dec 2001 00:45:33 -0800 [thread overview]
Message-ID: <3C0C8D2D.8060006@transmeta.com> (raw)
Hi,
I have hard-linked the prepatches I have been able to find into
/pub/linux/kernel/v*.*/testing/old/, following the "modern" naming
scheme, so the incdiff robot could produce incrementals against them.
First, I wanted to let you know what the deal was... they are just
hardlinks against what is elsewhere (/pub/linux/testing or
/pub/linux/people), with different names.
Second, there were several prepatches that did not apply cleanly, which
broke the robot, and which I had to remove from the testing/old
directories (I did not touch the original link, of course.) The only
one that was anywhere close to recent and might be worth fixing was
2.0.40-pre2; the other ones were 2.2.18 versions (-pre1,2,3,4, and 26.)
I mostly wanted to give you everyone a heads-up.
-hpa
reply other threads:[~2001-12-04 8:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C0C8D2D.8060006@transmeta.com \
--to=hpa@transmeta.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=tao@acc.umu.se \
--cc=torvalds@transmeta.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