[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ-Vmo=LtasH+qiKhbFpWZdHAMocR3_zZ5hr56quAqWu=Qs3gw@mail.gmail.com>
Date: Sat, 14 Apr 2012 19:06:00 -0400
From: Adrian Chadd <adrian@...ebsd.org>
To: Felipe Contreras <felipe.contreras@...il.com>
Cc: Stefan Richter <stefanr@...6.in-berlin.de>,
Greg KH <gregkh@...uxfoundation.org>,
Sergio Correia <lists@...e.net>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
linux-wireless Mailing List <linux-wireless@...r.kernel.org>,
Sujith Manoharan <c_manoha@....qualcomm.com>,
"ath9k-devel@...ts.ath9k.org" <ath9k-devel@...ema.h4ckr.net>,
"John W. Linville" <linville@...driver.com>
Subject: Re: [ 00/78] 3.3.2-stable review
Look, this is getting ridiculous.
I think you're completely wrapped up in the "git" way of thinking about things.
The patch can't be "dropped". It can't be "reverted". It can't be
"removed". All that Linus can do is apply a reversed patch. Then Greg
can sync up however he does it.
You seem completely wrapped up in some misguided notion that the patch
can be dropped from some series of patches. This isn't OpenWRT - you
don't have a directory of a hundred-odd patches. It's a source
revision system, complete with history. You don't remove a patch from
an existing repository - you commit a fix. That may be a reversed
version of the actual commit - but the effect is the same, the change
is "reverted". It just isn't removed from the history.
I think this is done and dusted. :-)
Adrian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists