All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Joe Perches <joe@perches.com>
Cc: David Miller <davem@davemloft.net>,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] split up feature-removal-schedule.txt
Date: Wed, 13 Feb 2008 08:59:24 -0800	[thread overview]
Message-ID: <20080213165924.GB10129@suse.de> (raw)
In-Reply-To: <1202887323.3129.10.camel@localhost>

On Tue, Feb 12, 2008 at 11:22:02PM -0800, Joe Perches wrote:
> On Tue, 2008-02-12 at 23:04 -0800, David Miller wrote:
> > > 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.
> 
> I suggest the same for MAINTAINERS

Why, is it a merge problem for you?

I've merged lots of new entries into it over the years, and never had a
problem with it, but that just might be me...

thanks,

greg k-h

  parent reply	other threads:[~2008-02-13 17:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  7:02 [GIT PATCH] split up feature-removal-schedule.txt Greg KH
2008-02-13  7:04 ` David Miller
2008-02-13  7:22   ` Joe Perches
2008-02-13 16:18     ` Randy Dunlap
2008-02-13 16:59     ` Greg KH [this message]
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=20080213165924.GB10129@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --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 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.