Thread (3 messages) flat view 3 messages, 2 authors, 2016-06-15

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:53:59

Matthew Ogilvie [off-list ref] writes:
Signed-off-by: Matthew Ogilvie <redacted>
---

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?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help