[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140925180005.GA11755@peff.net>
Date: Thu, 25 Sep 2014 14:00:05 -0400
From: Jeff King <peff@...f.net>
To: Joe Perches <joe@...ches.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Michal Sojka <sojka@...ica.cz>, linux-usb@...r.kernel.org,
Alan Stern <stern@...land.harvard.edu>,
Bryan Wu <cooloney@...il.com>, Felipe Balbi <balbi@...com>,
Linux LED Subsystem <linux-leds@...r.kernel.org>,
linux-kernel@...r.kernel.org, michal.vokac@...ap.cz,
git <git@...r.kernel.org>
Subject: Re: project wide: git config entry for [diff] renames=true
On Thu, Sep 25, 2014 at 08:48:31AM -0700, Joe Perches wrote:
> On Thu, 2014-09-25 at 17:03 +0200, Greg Kroah-Hartman wrote:
>
> > In the future, please generate a git "move" diff, which makes it easier
> > to review, and prove that nothing really changed. It also helps if the
> > file is a bit different from what you diffed against, which in my case,
> > was true.
>
> Maybe it'd be possible to add
>
> [diff]
> renames = true
>
> to the .git/config file.
>
> but I don't find a mechanism to add anything to the
> .git/config and have it be pulled.
There is no such mechanism within git. We've resisted adding one because
of the danger of something like:
[diff]
external = rm -rf /
diff.renames is probably safe, but any config-sharing mechanism would
have to deal with either whitelisting, or providing some mechanism for
the puller to review changes before blindly following them.
-Peff
--
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