Re: [PATCH v2 0/9] About the trailing slashes

2014-01-27 Thread Junio C Hamano
Thanks; will try to rebase on top of more recent codebase and then review. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH v2 0/9] About the trailing slashes

2014-01-24 Thread Nguyễn Thái Ngọc Duy
So this is the reroll that makes git diff HEAD submodule git diff HEAD submodule/ and git diff HEAD HEAD^ submodule git diff HEAD HEAD^ submodule/ behave the same way. The main patches are 04/09 and 09/09. The rest is just refactoring and cleaning up. While looking at this, I found a

Re: [PATCH v2 0/9] About the trailing slashes

2014-01-24 Thread Junio C Hamano
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes: While looking at this, I found a funny behavior of fill_directory. $ git init $ mkdir b $ b/c $ b/d $ git status b Untracked files: b/ $ git status b/ Untracked files: b/c b/d Notice how the trailing

Re: [PATCH v2 0/9] About the trailing slashes

2014-01-24 Thread Duy Nguyen
On Sat, Jan 25, 2014 at 2:22 AM, Junio C Hamano gits...@pobox.com wrote: How does git status '[b]/' behave? It outputs b/ (like git status b). I think that's because common_prefix_len() stops looking at the first wildcard char, '['. So common prefix is empty, just like b. -- Duy -- To