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

Re: [PATCH] Documentation: have ls-files and ls-tree "see also" each other

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 5, 2012, 05:43 UTC
Message-ID
<7vehpuqpob.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1338873037-4343-1-git-send-email-mmogilvi_git@miniinfo.net>
Matthew Ogilvie <mmogilvi_git@miniinfo.net> writes:
Show 6 quoted lines
> Signed-off-by: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
> ---
>
> I could have used these references when I was looking at git-ls-files
> documentation and trying to figure out how to make it list files
> from a specific commit like git-ls-tree.
I do not like this kind of patches in general.  Where will it end?

"I wanted to know how to list objects recorded in a commit, and I could have used a reference to git-ls-tree from git-commit, so here is a patch to make them refer to each other"?

That kind of overfiew is what the tutorial (for concepts like the index, tree objects, commit objects, etc.) and the list of commands in git(1). Is there compelling reason other than "I didn't bother to look, and it is likely other people wouldn't" to apply patches like this?

Previous: Matthew OgilvieNext: Matthew Ogilvie
Message 2 of 4 in “Documentation: have ls-files and ls-tree "see also" each other”
  1. Documentation: have ls-files and ls-tree "see also" each otherMatthew Ogilvie, Jun 5, 2012
  2. Junio C HamanoJun 5, 2012
  3. Matthew OgilvieJun 5, 2012
  4. Junio C HamanoJun 5, 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.