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

Re: Suggestions to make git easier to understand

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 11, 2011, 23:08 UTC
Message-ID
<20110811230807.GA5608@elie.gateway.2wire.net>
In-Reply-To
<7vmxffpo8e.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> I do not think "ls-files --contents" makes things any better, though.
> Until a new user encounters a conflicted state, it might look like that
> the primary point of "ls-files -s" is to show the object names, but it
> also is important that it shows the stage numbers.

Yes, sloppy of me. I should have said "the intent of these suggestions seems reasonable, and I believe that with minimal tweaking they would all lead to good things".

In the case of "ls-files -s", I suspect what would be most useful is a new porcelain "git ls --merge", building on Duy's work[*].

[*] http://thread.gmane.org/gmane.comp.version-control.git/166405/focus=166415
Previous: Junio C HamanoNext: Jeff King
Message 4 of 6 in “Suggestions to make git easier to understand”
  1. Philippe VaucherAug 11, 2011
  2. Jonathan NiederAug 11, 2011
  3. Junio C HamanoAug 11, 2011
  4. Jonathan NiederAug 11, 2011
  5. Jeff KingAug 12, 2011
  6. Philippe VaucherAug 15, 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.