From: Junio C Hamano <gitster@pobox•com>
To: Joe Perches <joe@perches•com>
Cc: Jeff King <peff@peff•net>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Michal Sojka <sojka@merica•cz>,
linux-usb@vger•kernel.org, Alan Stern <stern@rowland•harvard.edu>,
Bryan Wu <cooloney@gmail•com>, Felipe Balbi <balbi@ti•com>,
Linux LED Subsystem <linux-leds@vger•kernel.org>,
linux-kernel@vger•kernel.org, michal.vokac@comap•cz,
git <git@vger•kernel.org>
Subject: Re: project wide: git config entry for [diff] renames=true
Date: Thu, 25 Sep 2014 11:43:27 -0700 [thread overview]
Message-ID: <xmqq61gbbkxc.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1411668391.3460.2.camel@joe-AO725> (Joe Perches's message of "Thu, 25 Sep 2014 11:06:31 -0700")
Joe Perches <joe@perches•com> writes:
> On Thu, 2014-09-25 at 14:00 -0400, Jeff King wrote:
> ...
>> 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.
>
> Another mechanism might be to add a repository
> top level .gitconfig and add whatever to that.
That could be smaller half of an implementation detail of one of the
two possibilities Jeff mentioned i.e. "mechanism for the puller to
review changes before blindly following". It gives the transfer
part. You still need a new mechanism to make that file that is
tracked in the repository to be used as part of your configuration
variable set after letting the puller to review and approve.
A puller who blindly trust the project could use the "include"
mechanism from your .git/config to include a file with a well-known
name that is tracked by the project _without_ review or approval. I
doubt we would recommend that in an open source setting, though.
next prev parent reply other threads:[~2014-09-25 18:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.1409241106100.1580-100000@iolanthe.rowland.org>
[not found] ` <1411591401-5874-1-git-send-email-sojka@merica.cz>
[not found] ` <1411591401-5874-4-git-send-email-sojka@merica.cz>
[not found] ` <20140925150353.GA15325@kroah.com>
2014-09-25 15:48 ` project wide: git config entry for [diff] renames=true Joe Perches
2014-09-25 18:00 ` Jeff King
2014-09-25 18:06 ` Joe Perches
2014-09-25 18:43 ` Junio C Hamano [this message]
[not found] ` <20140925180005.GA11755-AdEPDUrAXsQ@public.gmane.org>
2014-09-25 18:53 ` Junio C Hamano
2014-09-25 18:55 ` Junio C Hamano
2014-10-03 1:37 ` [RFC/PATCH 0/2] Introduce safe-include config feature Rasmus Villemoes
2014-10-03 1:37 ` [RFC/PATCH 1/2] config: Add safe-include directive Rasmus Villemoes
2014-10-03 5:27 ` Junio C Hamano
2014-10-03 5:34 ` Junio C Hamano
2014-10-03 18:52 ` Junio C Hamano
2014-10-06 9:28 ` Rasmus Villemoes
2014-10-06 17:58 ` Junio C Hamano
2014-10-03 1:37 ` [RFC/PATCH 2/2] config: Add test of safe-include feature Rasmus Villemoes
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=xmqq61gbbkxc.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=balbi@ti$(echo .)com \
--cc=cooloney@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=joe@perches$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-leds@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=michal.vokac@comap$(echo .)cz \
--cc=peff@peff$(echo .)net \
--cc=sojka@merica$(echo .)cz \
--cc=stern@rowland$(echo .)harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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