On Mon, Jul 21, 2008 at 12:25:35AM +0200, Steve Frécinaux wrote: > The notice covers this behaviour: > if you are in the git/ subdirectory of your repository, it will pick > the tree corresponding to that directory instead of the root one if you > specify the root tree object id. > > Compare the output of both of those commands: > git-ls-tree cb44e6571708aa2792c73a289d87586fe3c0c362 > git-cat-file -p cb44e6571708aa2792c73a289d87586fe3c0c362 > --- > Documentation/git-ls-tree.txt | 4 ++++ > 1 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/Documentation/git-ls-tree.txt b/Documentation/git-ls-tree.txt > index 1cdec22..7cba394 100644 > --- a/Documentation/git-ls-tree.txt > +++ b/Documentation/git-ls-tree.txt > @@ -21,6 +21,10 @@ though - 'paths' denote just a list of patterns to match, e.g. so specifying > directory name (without '-r') will behave differently, and order of the > arguments does not matter. > > +Note that if you give ls-tree the sha1 id of a parent of the tree > +corresponding to the directory you're in, it will resolve that tree and list > +its contents instead of listing the contents of the tree you gave. > + > OPTIONS > ------- > <tree-ish>:: It's hard to make out what do you mean, the patch description is much clearer, paradoxically. Also, this in fact holds for the root tree instead of the parent tree, and the behaviour changes from "weird" to "simply broken" when you try to list a tree object that is _not_ the root project tree from within a subdirectory: git$ git ls-tree HEAD Documentation 040000 tree 066c25e86a44d4c7bde2d3e9b91e6891d752efa1 Documentation git/Documentation$ git ls-tree 066c25e86a44d4c7bde2d3e9b91e6891d752efa1 git/Documentation$ I think that ls-tree simply shouldn't auto-fill its pathspec based on current prefix in case no pathspec was supplied. Patch to follow. -- Petr "Pasky" Baudis As in certain cults it is possible to kill a process if you know its true name. -- Ken Thompson and Dennis M. Ritchie -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
