mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gregkh@suse.de
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] split up feature-removal-schedule.txt
Date: Tue, 12 Feb 2008 23:04:23 -0800 (PST)	[thread overview]
Message-ID: <20080212.230423.172781444.davem@davemloft.net> (raw)
In-Reply-To: <20080213070215.GA11969@kroah.com>

From: Greg KH <gregkh@suse.de>
Date: Tue, 12 Feb 2008 23:02:15 -0800

> In the big "linux-next" series of emails, David Miller suggested that
> the feature-removal-schedule file be broken up into little pieces, as it
> is causing merge problems for different trees.
> 
> This changeset does just that.  Turns out that this makes things more
> readable, as it's easier to look at a list of filenames for things than
> picking through a 300 line text file.
> 
> Please pull from:
> 	master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6.git/

Acked-by: David S. Miller <davem@davemloft.net>

Thanks for doing this work.

  reply	other threads:[~2008-02-13  7:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  7:02 Greg KH
2008-02-13  7:04 ` David Miller [this message]
2008-02-13  7:22   ` Joe Perches
2008-02-13 16:18     ` Randy Dunlap
2008-02-13 16:59     ` Greg KH
2008-02-13 17:33       ` Joe Perches
2008-02-13 17:47         ` Greg KH
2008-02-13 18:13         ` Linus Torvalds
2008-02-13 18:19           ` Linus Torvalds
2008-02-13 23:38             ` Junio C Hamano
2008-02-13 19:32           ` Andrew Morton
2008-02-19 19:07           ` Greg KH
2008-02-19 19:34             ` Randy Dunlap
2008-02-19 19:49               ` Greg KH
2008-02-19 20:06                 ` Adrian Bunk
2008-02-13  7:27 ` KOSAKI Motohiro
2008-02-13 10:30 ` [GIT PATCH] " Pekka Pietikainen
2008-02-13 17:00   ` Greg KH
2008-02-13 12:11 ` Jeff Garzik

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=20080212.230423.172781444.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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
all inboxes | Powered by JetHome®