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

Re: Future suggestion's to assist with changes to git.

From
BGBoyd Lynn Gerber <gerberb@zenez.com>
Date
Aug 29, 2008, 00:50 UTC
Message-ID
<alpine.LNX.1.10.0808281849120.26701@suse104.zenez.com>
In-Reply-To
<F50DF26D-3CD3-4A20-BAFB-758D0441CD00@cs.indiana.edu>
On Thu, 28 Aug 2008, Perry Wagle wrote:
Show 6 quoted lines
> Here's my relevant paragraph from the other thread:
>
> I think the lesson here, however, it that the correct way to have done this 
> is to first remove all the git<DASH>'s from the source, demos, sample, 
> documentation, etc.  Second, BIG PAUSE (full minor version release cycle?) 
> Then, third, get rid of git<DASH> in <prefix>/bin.

Thanks, I think having all the suggestions in one place without having to go through the long thread is a good idea.

Thanks,

-- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047

Previous: Perry Wagle
Message 10 of 10 in “Future suggestion's to assist with changes to git.”
  1. Boyd Lynn GerberAug 28, 2008
  2. Jeff KingAug 28, 2008
  3. Boyd Lynn GerberAug 28, 2008
  4. Jeff KingAug 28, 2008
  5. Gerrit PapeAug 29, 2008
  6. Junio C HamanoAug 28, 2008
  7. Jeff KingAug 29, 2008
  8. Boyd Lynn GerberAug 29, 2008
  9. Perry WagleAug 29, 2008
  10. Boyd Lynn GerberAug 29, 2008

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.