From: Duy Nguyen <pclouds@gmail.com>
To: Cameron Esfahani <dirty@apple.com>
Cc: Git Mailing List <git@vger.kernel.org>, Paul Tan <pyokagan@gmail.com>
Subject: Re: -C option with pull doesn't seem to be respected in aliases in git 2.6.4.
Date: Mon, 21 Dec 2015 16:57:09 +0700 [thread overview]
Message-ID: <CACsJy8BDCqX4+i0krS-8Xq2q-4-siwdCcG5+Maqa8XEUU3sVOg@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8D=a4NUi+zWj=DVrzRdCxzWA6hp8kCaPAN_Cwv7H7Ohkg@mail.gmail.com>
On Mon, Dec 21, 2015 at 8:17 AM, Duy Nguyen <pclouds@gmail.com> wrote:
> On Fri, Dec 18, 2015 at 8:35 AM, Cameron Esfahani <dirty@apple.com> 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
prev parent reply other threads:[~2015-12-21 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 1:35 -C option with pull doesn't seem to be respected in aliases in git 2.6.4 Cameron Esfahani
2015-12-21 1:17 ` Duy Nguyen
2015-12-21 9:57 ` Duy Nguyen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACsJy8BDCqX4+i0krS-8Xq2q-4-siwdCcG5+Maqa8XEUU3sVOg@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=dirty@apple.com \
--cc=git@vger.kernel.org \
--cc=pyokagan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).