From: Junio C Hamano <gitster@pobox.com>
To: Christopher Lindee <christopher.lindee@webpros.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 0/2] Optionally support push options on up-to-date branches
Date: Fri, 15 Mar 2024 08:42:51 -0700 [thread overview]
Message-ID: <xmqqil1ntsas.fsf@gitster.g> (raw)
In-Reply-To: <PH0PR14MB4702D85D5D40F910A97B49E98D282@PH0PR14MB4702.namprd14.prod.outlook.com> (Christopher Lindee's message of "Fri, 15 Mar 2024 00:19:57 +0000")
Christopher Lindee <christopher.lindee@webpros.com> writes:
> Junio C Hamano writes:
>
>> In any case, I am OK with the feature. I just was wondering if the
>> end-user experience may become simpler and easier if we did not have
>> to have a command line option.
>
> I think we should have the command line option, if only for backwards
> compatibility. The question on my mind is: do we default to on or off?
It seems like the concensus is we want this as an opt-in feature.
Defaults off, with an explicit command line option.
Thanks.
next prev parent reply other threads:[~2024-03-15 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 21:55 [PATCH 0/2] Optionally support push options on up-to-date branches Christopher Lindee
2024-03-13 22:58 ` Junio C Hamano
2024-03-14 22:55 ` brian m. carlson
2024-03-14 23:29 ` Junio C Hamano
2024-03-15 0:04 ` Chris Torek
2024-03-15 0:57 ` brian m. carlson
2024-03-15 0:19 ` Christopher Lindee
2024-03-15 15:42 ` Junio C Hamano [this message]
2024-03-15 0:39 ` brian m. carlson
2024-03-15 8:58 ` Christopher Lindee
2024-03-15 20:29 ` brian m. carlson
2024-03-15 0:11 ` Christopher Lindee
2024-03-14 23:08 ` Christopher Lindee
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqil1ntsas.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christopher.lindee@webpros.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).