public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Peter Yao <peter@exavio.com.cn>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to get individual -ac patches?
Date: Fri, 7 May 2004 00:33:40 +0200	[thread overview]
Message-ID: <20040506223340.GV9636@fs.tum.de> (raw)
In-Reply-To: <40833514.3080200@exavio.com.cn>

On Mon, Apr 19, 2004 at 10:10:28AM +0800, Peter Yao wrote:

> Hi,

Hi Peter,

> Is there a repository that stores individual -ac patches for 2.4 but not
> a big patch set? What I mean is a lot small patches that can be applied
> one by one. I tried kernel.org and others but found only big patch sets.

-ac was always only available as one big patch.

> Thanks.
> 
> Peter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2004-05-06 22:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19  2:10 How to get individual -ac patches? Peter Yao
2004-05-06 22:33 ` Adrian Bunk [this message]

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=20040506223340.GV9636@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@exavio.com.cn \
    /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