On Mon, Dec 21, 2015 at 8:17 AM, Duy Nguyen <pclouds@xxxxxxxxx> wrote:
> On Fri, Dec 18, 2015 at 8:35 AM, Cameron Esfahani <dirty@xxxxxxxxx> wrote:
>> I have git project checked out at ~/llvm. Inside of there, inside of a “tools” directory, I have another project checked out as “lldb”:
>>
>> ~/llvm/tools/lldb
>>
>> I wrote an alias which would help me update all my projects:
>>
>> all = !find . -type d -name .git | sed 's:/.git::' | xargs -I{} -t git -C {} $1 && :
>>
>> This would allow me to be inside of ~/llvm and type "git all pull" and get all my projects updated.
>>
>> It seems that at some point this broke. If try to use this alias under git 2.6.4, it only updates the llvm project.
>>
>> The interesting thing is that if I pass fetch, instead of pull: "git all fetch", then it seems to work correctly.
Because the difference between git-fetch and git-pull in git.c is
NEED_WORK_TREE. Can you try to unset GIT_WORK_TREE before "find"? This
could be yet another regression from d95138e (setup: set env
$GIT_WORK_TREE when work tree is set, like $GIT_DIR - 2015-06-26)
--
Duy
--
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