git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: RFC/Discussion - Submodule UX Improvements

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Apr 19, 2021, 12:56 UTC
Message-ID
<00dc01d7351b$6ffc6500$4ff52f00$@nexbridge.com>
In-Reply-To
<YHofmWcIAidkvJiD@google.com>
> -----Original Message-----
> From: Emily Shaffer <emilyshaffer@google.com>
On April 16, 2021 7:37 PM, Emily Shaffer wrote:
> As hinted by a couple recent patches, I'm planning on some pretty big
> submodule work over the next 6 months or so - and Ævar pointed out to me
in
> https://lore.kernel.org/git/87v98p17im.fsf@evledraar.gmail.com that I
> probably should share some of those plans ahead of time. :) So attached is
a
> lightly modified version of the doc that we've been working on internally
at
> Google, focusing on what we think would be an ideal submodule workflow.
> 
> I'm hoping that folks will get a chance to read some or all of it and let
us know
> what sounds cool (or sounds extremely broken). The best spot to start is
> probably the "Overview" section, which describes what the "main path"
would
> look like for a user working on a project with submodules. Most of the
work
> that we're planning on doing is under the "What doesn't already work"
> headings.
> 
> Thanks in advance for any time you spend reading/discussing :)
<big snip>

Just adding my voice here, this is something my teams would be very happy to consider.

> - Worktrees
> When a user runs 'git worktree add' from the superproject, each submodule
>  in the new worktree should also be created as a worktree of the
corresponding
>  submodule in the original project.
> What doesn't already work:
>   * worktrees and submodules getting along - submodules are now freshly
cloned
>     when creating a superproject worktree

My teams are currently debating the use of submodules (we have gone back and forth over the years on these) and worktrees (which seem to have some positive process implications for those more legacy-ish team members more used to a centralised workflows). I have not seen any worktree/submodule combinations used but fear the worst - as in I'm pretty sure I know which of my team members is going to try this. It is probably a separate matter to make the two get along better.

Cheers, Randall

-- Brief whoami: NonStop developer since approximately 211288444200000000 UNIX developer since approximately 421664400 -- In my real life, I talk too much.

Previous: Philippe BlainNext: Aaron Schrab
Message 8 of 18 in “RFC/Discussion - Submodule UX Improvements”
  1. Emily ShafferApr 16, 2021
  2. Christian CouderApr 18, 2021
  3. Emily ShafferApr 20, 2021
  4. Philippe BlainApr 19, 2021
  5. Emily ShafferApr 20, 2021
  6. Junio C HamanoApr 20, 2021
  7. Philippe BlainApr 21, 2021
  8. Randall S. BeckerApr 19, 2021
  9. Aaron SchrabApr 19, 2021
  10. Emily ShafferApr 20, 2021
  11. Randall S. BeckerApr 20, 2021
  12. Jacob KellerApr 19, 2021
  13. Randall S. BeckerApr 19, 2021
  14. Jacob KellerApr 20, 2021
  15. Emily ShafferApr 20, 2021
  16. Randall S. BeckerApr 20, 2021
  17. Jacob KellerApr 21, 2021
  18. Jacob KellerApr 22, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.