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

Re: [PATCH] Remove deprecated OPTION_BOOLEAN

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 29, 2013, 17:58 UTC
Message-ID
<7vbo5l1c5a.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1375112281-3935-1-git-send-email-stefanbeller@googlemail.com>
Stefan Beller <stefanbeller@googlemail.com> writes:
Show 5 quoted lines
> So recently Junio released -rc0. Is that a reason to not
> send out patches, which do not do bugfixes? So the following 
> commit for example doesn't fix a bug nor does it add a feature.
> Is it fine to send out such kind of commits during the -rc
> times or better wait for the next development cycle?

It would be a good idea to show it to others as a preview of what to come even in a pre-release freeze period, so that people holding real patches in the affected area can work with you to avoid conflicts.

But I would not expect them to be applied to the upcoming release, nor even 'next'---this largely depends on the maintainer workload.

Thanks.
Previous: Stefan BellerNext: Stefan Beller
Message 5 of 7 in “Remove deprecated OPTION_BOOLEAN”
  1. Remove deprecated OPTION_BOOLEANStefan Beller, Jul 29, 2013
  2. Remove deprecated OPTION_BOOLEANStefan Beller, Jul 29, 2013
  3. Junio C HamanoJul 29, 2013
  4. Stefan BellerJul 29, 2013
  5. Junio C HamanoJul 29, 2013
  6. Stefan BellerJul 29, 2013
  7. Junio C HamanoJul 29, 2013

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.