From: Felipe Contreras <felipe.contreras@gmail.com>
To: Krzysztof Mazur <krzysiek@podlesie.net>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3] Add core.mode configuration
Date: Wed, 16 Oct 2013 14:28:21 -0500
Message-ID: <525ee8d5ba989_3983c19e7c8b@nysa.notmuch> (raw)
In-Reply-To: <20131016063436.GB24964@shrek.podlesie.net>
Krzysztof Mazur wrote:
> On Tue, Oct 15, 2013 at 11:03:26PM -0500, Felipe Contreras wrote:
> > > not some "next" behavior that may change in future.
> >
> > But I'm suggesting to add a core.addremove option as well, like you suggested,
> > am I not?
>
> Yes, I think we both agreed on adding core.addremove. I'm just not
> convinced if we should also add core.mode.
If we add core.addremove, all the issues you mentioned are solved. If we do
that, now the question is, how exactly does core.mode = next affect anybody
genatively? If you don't like it, you don't set it, that's why it's a
configuration. I don't see the problem.
> > So you would be happy if we had core.addremove = true *and* core.mode = next,
> > right? You would use one, different people with different needs would use the
> > other.
>
> Yes, if there are people that will use core.mode it will be worth
> adding. I'm just not one of them.
I am already using it.
--
Felipe Contreras
prev parent reply index
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 7:04 Felipe Contreras
2013-10-14 20:59 ` Krzysztof Mazur
2013-10-14 21:35 ` Felipe Contreras
2013-10-15 12:35 ` Krzysztof Mazur
2013-10-15 12:32 ` Felipe Contreras
2013-10-15 13:33 ` Krzysztof Mazur
2013-10-15 13:29 ` Felipe Contreras
2013-10-15 14:51 ` Krzysztof Mazur
2013-10-15 16:59 ` John Szakmeister
2013-10-16 3:55 ` Felipe Contreras
2013-10-16 7:09 ` Krzysztof Mazur
2013-10-16 19:31 ` Felipe Contreras
2013-10-16 10:54 ` John Szakmeister
2013-10-16 15:11 ` John Szakmeister
2013-10-16 19:57 ` Felipe Contreras
2013-10-16 19:32 ` Felipe Contreras
2013-10-16 22:02 ` Philip Oakley
2013-10-16 23:06 ` Jonathan Nieder
2013-10-17 19:48 ` Philip Oakley
2013-10-17 21:08 ` Felipe Contreras
2013-10-15 18:51 ` Felipe Contreras
2013-10-15 22:01 ` Krzysztof Mazur
2013-10-16 4:03 ` Felipe Contreras
2013-10-16 6:34 ` Krzysztof Mazur
2013-10-16 19:28 ` Felipe Contreras [this message]
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=525ee8d5ba989_3983c19e7c8b@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=krzysiek@podlesie.net \
/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
Git Mailing List Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/git/0 git/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 git git/ https://lore.kernel.org/git \
git@vger.kernel.org
public-inbox-index git
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.kernel.vger.git
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git