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: Tue, 15 Oct 2013 23:03:26 -0500 Message-ID: <525e100e45ee8_81a151de74ed@nysa.notmuch> (raw) In-Reply-To: <20131015220125.GA14021@shrek.podlesie.net> Krzysztof Mazur wrote: > On Tue, Oct 15, 2013 at 01:51:41PM -0500, Felipe Contreras wrote: > > > > I don't see what is the problem. We haven't had the need for push.default = > > simplewarning, have we? If you want the warning, you don't change anything, if > > simplewarning makes no sense, because push.default=simple sets exact > behavior, Exactly. > 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? That option wouldn't change in the future. > > you want to specify something, you already know what you are doing. > > > > > Maybe we should also add core.mode=next-warn that changes defaults like next > > > but keeps warnings enabled until the user accepts that change by setting > > > appropriate config option? > > > > Maybe, but would you actually use that option? > > No. 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. > > > That's safer than next (at least for interactive use) and maybe more users > > > would use that, but I don't think that's worth adding. > > > > Maybe, but I don't think many users would use either mode, and that's good. > > > > > For me, old behavior by default and warnings with information how to > > > enable new incompatible features, is sufficient. So I don't need > > > core.mode option, but as long it will be useful for other users I have > > > nothing against it. > > > > OK, but that seems to mean you don't need core.mode = next-warn either. I'm not > > against adding such a mode, but I would like to hear about _somebody_ that > > would like to actually use it. I don't like to program for ghosts. > > > > As I said earlier, I don't think that next-warn it's worth adding, but > such option might increase the number of people interested in the > core.mode. Well that's a hypothesis, and I would be interested in finding out if that's true, but until I see somebody that says "I want core.mode = next-war", I'm going to assume they are hypothetical. -- Felipe Contreras
next 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 [this message] 2013-10-16 6:34 ` Krzysztof Mazur 2013-10-16 19:28 ` Felipe Contreras
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=525e100e45ee8_81a151de74ed@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