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

Re: What's cooking in git.git (May 2011, #13; Mon, 30)

From
Junio C Hamano <gitster@pobox.com>
Date
May 31, 2011, 06:21 UTC
Message-ID
<7v39jvl79w.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4DE4857A.70605@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
Show 5 quoted lines
> ... But as far as I am concerned, I do not mind backing out changes
> that break on Windows until a solution is found.
>
> [*] I do include cooking topics where I think that there is a chance that
> they break on Windows.

Very much appreciated. We want more people to help keeping the tip of "master" stable by running "next", or selected topics in it that may affect you in the future, like you do. Hearing that "master" is broken due to recent merge of topic X is, while better than hearing the same after the tip of "master" is tagged, a bit saddening, as the reason "next" exists in the first place is exactly to prevent such accidents by catching buggy topics while they are in "next".

Thanks.
Previous: Johannes Sixt
Message 7 of 7 in “What's cooking in git.git (May 2011, #13; Mon, 30)”
  1. Junio C HamanoMay 30, 2011
  2. Ævar Arnfjörð BjarmasonMay 30, 2011
  3. Johannes SixtMay 30, 2011
  4. Ævar Arnfjörð BjarmasonMay 30, 2011
  5. Junio C HamanoMay 30, 2011
  6. Johannes SixtMay 31, 2011
  7. Junio C HamanoMay 31, 2011

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.