cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Merging status.
Date: Thu, 28 Apr 2005 19:50:52 -0400	[thread overview]
Message-ID: <20050428235051.GC1730@redhat.com> (raw)
In-Reply-To: <20050428154033.248b5087.akpm@osdl.org>

On Thu, Apr 28, 2005 at 03:40:33PM -0700, Andrew Morton wrote:
 > Dave Jones <davej@redhat.com> wrote:
 > >
 > > [fixed up the Cc list which I botched]
 > > 
 > > On Thu, Apr 28, 2005 at 02:45:40PM -0700, Andrew Morton wrote:
 > >  > Dave Jones <davej@redhat.com> wrote:
 > >  > >
 > >  > > http://www.codemonkey.org.uk/projects/cpufreq/pending-patches/
 > >  > > http://www.codemonkey.org.uk/projects/agp/pending-patches/
 > >  > 
 > >  > No probs.  I'm already doing that for ALSA patches.
 > >  > 
 > >  > Please make sure the patches alphasort into applying order, or, when you
 > >  > start using quilt (you should!), include the series file.
 > > 
 > > They're of the form CPUFREQ-nn where nn is the numerical order they
 > > should be applied in.
 > 
 > Yeah, I always found that to be a bit unweildy.  Whatever.
 > 
 > For some bizarre reason, your http server manages to break wget.
 > 
 > 	wget -r http://www.codemonkey.org.uk/projects/cpufreq/pending-patches
 > 
 > doesn't fetch the patches.  Confused.

Fixed.

		Dave

  parent reply	other threads:[~2005-04-28 23:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2005-04-29  0:09         ` Andrew Morton
2005-04-29  0:12           ` Dave Jones
2005-04-28 20:47 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=20050428235051.GC1730@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox