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 08:17:26 +0700 [thread overview]
Message-ID: <CACsJy8D=a4NUi+zWj=DVrzRdCxzWA6hp8kCaPAN_Cwv7H7Ohkg@mail.gmail.com> (raw)
In-Reply-To: <96FA4EE3-B68F-49B9-896F-38F37E12676D@apple.com>
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.
It would help if you could bisect this to the first broken commit (or
at least one version that works). git-pull was rewritten in C in
2.6.0, so this could be a regression. If you try a version before that
and the problem remains, then it's not the git-pull rewrite. Another
suspect is c056261 (git potty: restore environments after alias
expansion - 2014-06-08), since v2.1.0.
--
Duy
next prev parent reply other threads:[~2015-12-21 1:18 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 [this message]
2015-12-21 9:57 ` Duy Nguyen
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='CACsJy8D=a4NUi+zWj=DVrzRdCxzWA6hp8kCaPAN_Cwv7H7Ohkg@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).