From: Junio C Hamano Date: Tue, 05 Jun 2012 05:43:32 GMT Subject: Re: [PATCH] Documentation: have ls-files and ls-tree "see also" each other Message-ID: <7vehpuqpob.fsf@alter.siamese.dyndns.org> In-Reply-To: <1338873037-4343-1-git-send-email-mmogilvi_git@miniinfo.net> Matthew Ogilvie writes: > Signed-off-by: Matthew Ogilvie > --- > > 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?