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

Re: [PATCH,v2] contrib/examples/README: give an explanation of the status of these files

From
Andreas Ericsson <ae@op5.se>
Date
Jan 13, 2009, 13:43 UTC
Message-ID
<496C9A66.5000909@op5.se>
In-Reply-To
<18071eea0901130201r41c576e6t7f8c9fda7259e9f2@mail.gmail.com>
Thomas Adam wrote:
Show 9 quoted lines
> 2009/1/13  <jidanni@jidanni.org>:
>> @@ -0,0 +1,3 @@
>> +These are original scripted implementations, kept primarily for their
>> +reference value to any aspiring plumbing users who want to learn how
>> +pieces can be fit together.
> 
> "... who want to learn how the pieces fit together" is the correct
> phrasing.  The above is incorrect.
>

Actually, "can be fitted together" would be correct, as we're not talking about a jigsaw puzzle with just one solution, but rather a few possible ways of building something out of the lego-style programs that make up git.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231
Previous: Thomas Adam
Message 6 of 6 in “contrib/examples/README: warn of obsolescence”
  1. contrib/examples/README: warn of obsolescencejidanni@jidanni.org, Jan 13, 2009
  2. Junio C HamanoJan 13, 2009
  3. contrib/examples/README: give an explanation of the status of these filesjidanni@jidanni.org, Jan 13, 2009
  4. Junio C HamanoJan 13, 2009
  5. Thomas AdamJan 13, 2009
  6. Andreas EricssonJan 13, 2009

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.