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

Re: [PATCH] Third try at documenting command integration requirements.

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 28, 2012, 01:58 UTC
Message-ID
<7vobiijxol.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20121127175618.GA11845@thyrsus.com>
"Eric S. Raymond" <esr@thyrsus.com> writes:
Show 8 quoted lines
> I agree that 2.4 is still quite OK.  I'm a little concerned that dropping that
> far back might store up some transition problems for the day we decide to
> make the jump to Python 3.
>
> On the other hand, I think gating features on RHEL5 might be
> excessively cautious.  According to [1], RHEL will red-zone within 30
> days if it hasn't done so already ([1] says "Q4").  And RHEL6 (with
> Python 2.6) has been shipping for two years.

I won't worry about Python 3 yet; in what timeframe did Python's i18n/unicode support become usable? In 2.4, or 2.6?

Previous: Eric S. RaymondNext: Eric S. Raymond
Message 7 of 10 in “Third try at documenting command integration requirements.”
  1. Third try at documenting command integration requirements.Eric S. Raymond, Nov 26, 2012
  2. Perry HutchisonNov 26, 2012
  3. Junio C HamanoNov 26, 2012
  4. Eric S. RaymondNov 26, 2012
  5. Michael HaggertyNov 27, 2012
  6. Eric S. RaymondNov 27, 2012
  7. Junio C HamanoNov 28, 2012
  8. Eric S. RaymondNov 28, 2012
  9. Junio C HamanoNov 26, 2012
  10. Eric S. RaymondNov 26, 2012

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.