From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2020, #04; Tue, 22)
Date: Tue, 22 Dec 2020 15:25:35 -0500 [thread overview]
Message-ID: <CAPig+cT7q76NMubK3N2R-OmRUnH6HVWOt7eKRNCVjtv_qWK97g@mail.gmail.com> (raw)
In-Reply-To: <xmqqo8ilhafa.fsf@gitster.c.googlers.com>
On Tue, Dec 22, 2020 at 3:08 PM Junio C Hamano <gitster@pobox.com> wrote:
> * es/worktree-repair-both-moved (2020-12-21) 1 commit
> - worktree: teach `repair` to fix multi-directional breakage
>
> "git worktree repair" learned to take advantage of the fact that it
> knows both ends (i.e. the main repository is found in the location
> the command runs, the worktrees are given as arguments) to deal
> with the case where both the repository and the worktree moved.
The lengthy parenthetical comment makes this description a bit
difficult to digest. I had to read it a couple times to understand
what it was saying. Perhaps it could be simplified, perhaps like this:
"git worktree repair" learned to handle the case when both the
repository and worktrees have been moved.
By the way, an unrelated patch[1] I sent a day before sending the
es/worktree-repair-both-moved topic doesn't seem to have made it into
'seen', so I'm wondering if it was overlooked (or perhaps it just
hasn't been processed yet).
[1]: https://lore.kernel.org/git/20201220212740.44273-1-sunshine@sunshineco.com/
next prev parent reply other threads:[~2020-12-22 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 20:07 What's cooking in git.git (Dec 2020, #04; Tue, 22) Junio C Hamano
2020-12-22 20:25 ` Eric Sunshine [this message]
2020-12-22 21:46 ` Junio C Hamano
2020-12-23 7:46 ` Patrick Steinhardt
2020-12-23 20:59 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cT7q76NMubK3N2R-OmRUnH6HVWOt7eKRNCVjtv_qWK97g@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).