From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: Joe Perches <public-joe-6d6DIl74uiNBDgjK7y7TUQ@plane•gmane.org>,
git@vger•kernel.org
Subject: Re: project wide: git config entry for [diff] renames=true
Date: Thu, 25 Sep 2014 11:55:32 -0700 [thread overview]
Message-ID: <xmqqtx3va5sr.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqqy4t7a5vx.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Thu, 25 Sep 2014 11:53:38 -0700")
Junio C Hamano <gitster-e+AXbWqSrlAAvxtiuMwx3w@public•gmane.org>
writes:
> or even
>
> [config]
> safe = !*
> ...
Gaah, I meant [include] in all places I spelled [config] in the
previous message.
next prev parent reply other threads:[~2014-09-25 18:55 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
[not found] ` <20140925180005.GA11755-AdEPDUrAXsQ@public.gmane.org>
2014-09-25 18:53 ` Junio C Hamano
2014-09-25 18:55 ` Junio C Hamano [this message]
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=xmqqtx3va5sr.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
--cc=public-joe-6d6DIl74uiNBDgjK7y7TUQ@plane$(echo .)gmane.org \
/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