Re: [PATCH 0/4] Link worktrees with relative paths

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Oct 6, 2024, 22:24 UTC
Message-ID: <CAPig+cRzvKddHsqahndU-pnScqNB9tL1KR-XBBGB6wx6U9v40w@mail.gmail.com>
In-Reply-To: <w7hncKNNAlJFs7fyi_ZzMj8iNF-GMgbm3E-7Wit9qUey2FDVTwj0CKg_Youi3mPpOcBvDEWyVEaeryeL10LqAY002FdBxBpi7zTQervXgyM=@pm.me>

On Sun, Oct 6, 2024 at 6:08 PM Caleb White <cdwhite3@pm.me> wrote:

Show 5 quoted lines

> On Sunday, October 6th, 2024 at 02:45, Eric Sunshine <sunshine@sunshineco.com> wrote:
> > Can you try GitGitGadget instead (preferable) or perhaps publish this
> > series somewhere (less preferable).
>
> I just created a GGG PR [1], can someone please give me /access?

Done.

> Speaking of which, is there a way to tell GGG that I want to start on v3 to
> keep the continuity? I suppose I could always just reference the other versions
> in the PR body but I wasn't sure if there were other commands available besides
> just `/submit`.

Um, I'm not a GitGitGadget user, so I can't say definitively, but I don't believe there is a way to do that.

Referencing the previous versions is always appreciated by reviewers anyhow since it makes their task simpler. In particular, in the cover commentary for any given version, reviewers like to see an explanation of the series, references to previous versions, and a prose description of what has changed in the current version as compared with the previous version. Reviewers also really appreciate seeing a mechanically-generated difference between versions, such as generated by `git format-patch --cover-letter --range-diff=...`, or generated automatically by GitGitGadget.