From: Dave Jones <davej@redhat.com>
To: cpufreq@lists.linux.org.uk
Subject: Merging status.
Date: Thu, 28 Apr 2005 16:47:19 -0400 [thread overview]
Message-ID: <20050428204719.GG8514@redhat.com> (raw)
So, I've finally got around to extracting the bits that were
in the cpufreq bitkeeper tree, and exported them all as
GNU diffs for the time being.
These will go off to Linus pretty soon.
I'll set up a script to auto-mirror cpufreq changes that
I've got queued for merging. They'll appear at
http://www.codemonkey.org.uk/projects/cpufreq/pending-patches/
Treat this directory the same as you treated
"merged into cpufreq-bk".
(Ie, Andrew can just set up a wget -r on this dir for each -mm
[theres also a http://www.codemonkey.org.uk/projects/agp/pending-patches/
for Andrews info])
I may look into using git at a later time, but right now its
probably going to be easier to just throw patches around.
Dave
next reply other threads:[~2005-04-28 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 20:47 Dave Jones [this message]
[not found] <20050428203740.GE8514@redhat.com>
[not found] ` <20050428144540.62936aa8.akpm@osdl.org>
2005-04-28 22:13 ` Merging status Dave Jones
2005-04-28 22:40 ` Andrew Morton
2005-04-28 23:03 ` Andrew Morton
2005-04-28 23:50 ` Dave Jones
2005-04-29 0:09 ` Andrew Morton
2005-04-29 0:12 ` Dave Jones
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=20050428204719.GG8514@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.