git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] Optionally support push options on up-to-date branches

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 15, 2024, 15:42 UTC
Message-ID
<xmqqil1ntsas.fsf@gitster.g>
In-Reply-To
<PH0PR14MB4702D85D5D40F910A97B49E98D282@PH0PR14MB4702.namprd14.prod.outlook.com>
Christopher Lindee <christopher.lindee@webpros.com> writes:
Show 8 quoted lines
> 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.
Previous: Christopher LindeeNext: brian m. carlson
Message 8 of 13 in “Optionally support push options on up-to-date branches”
  1. 0/2 Optionally support push options on up-to-date branchesChristopher Lindee, Mar 12, 2024
  2. Junio C HamanoMar 13, 2024
  3. brian m. carlsonMar 14, 2024
  4. Junio C HamanoMar 14, 2024
  5. Chris TorekMar 15, 2024
  6. brian m. carlsonMar 15, 2024
  7. Christopher LindeeMar 15, 2024
  8. Junio C HamanoMar 15, 2024
  9. brian m. carlsonMar 15, 2024
  10. Christopher LindeeMar 15, 2024
  11. brian m. carlsonMar 15, 2024
  12. Christopher LindeeMar 15, 2024
  13. Christopher LindeeMar 14, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.