From: Junio C Hamano <gitster@pobox.com>
To: XZS <d.f.fischer@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/GSoC] add a add.patch config variable
Date: Thu, 24 Mar 2016 14:20:30 -0700 [thread overview]
Message-ID: <xmqqvb4b7eu9.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1458853787-29807-2-git-send-email-d.f.fischer@web.de> (XZS's message of "Thu, 24 Mar 2016 22:09:47 +0100")
XZS <d.f.fischer@web.de> writes:
> Users may like to review their changes when staging by default. It is
> also a convenient safety feature for beginners nudging them to have a
> second look at their changes when composing a commit.
>
> To this end, the config variable allows to have git-add to always act
> like -p was passed.
Now with such a configuration in her ~/.gitconfig, how would she
ever run the normal "git add", which perhaps is invoked by one of
the scripts she regularly uses? E.g. "git mergetool"?
next prev parent reply other threads:[~2016-03-24 21:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 21:09 [GSoC] Proposal XZS
2016-03-24 21:09 ` [PATCH/GSoC] add a add.patch config variable XZS
2016-03-24 21:20 ` Junio C Hamano [this message]
2016-03-25 0:43 ` Dominik Fischer
2016-03-25 6:30 ` Junio C Hamano
2016-04-21 9:15 ` [PATCH/RFC/GSoC 0/2] " XZS
2016-04-21 9:15 ` [PATCH/RFC/GSoC 1/2] count recursion depth XZS
2016-04-21 9:15 ` [PATCH/RFC/GSoC 2/2] add a add.patch config variable XZS
2016-04-21 15:39 ` [PATCH/RFC/GSoC 0/2] " Johannes Schindelin
2016-04-21 16:30 ` Dominik Fischer
2016-04-21 16:43 ` Matthieu Moy
2016-04-21 16:47 ` Junio C Hamano
2016-04-21 17:28 ` Dominik Fischer
2016-04-22 6:45 ` Johannes Schindelin
2016-04-22 6:42 ` Johannes Schindelin
2016-03-25 7:01 ` [PATCH/GSoC] " Christian Couder
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=xmqqvb4b7eu9.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=d.f.fischer@web.de \
--cc=git@vger.kernel.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.