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

Re: "git overlay" - command for overlaying branches

From
OBOliver Bandel <oliver@first.in-berlin.de>
Date
Dec 1, 2023, 00:11 UTC
Message-ID
<6wyjngq772jjy5hbydegblbrviuvama4avyxof2olkjpey3ohi@drpwcb2eothu>
In-Reply-To
<20231125105046.GB9696@kitsune.suse.cz>
What I basically want to do is:
- Working on more than one branch at the same time.
- Having all checked-out branches together in one working dir.
- When adding/committing, all checked-out files will be added/committed
  to those branches, from where they were checked out.

This way I could edit multiple branches simultaneously independently without the need of merging. Merging can be done later on, if needed.

Possible alternatives?

For the multiple checkouts I could do a workaround and use a local bare-repo and check out each branch of interest into a seperate directory. I could then edit the files from the different dirs.

But for the overlaying thing, to get the files into one dir (with the automatic hiding of equally named files from branches that were overlayed before) it would need something like a FUSE-based tool, so that all the branches could be blended into one working dir.

A "git overlay" would make this easier. No extra bare-repo needed, no additional tool for blending the dirs needed.

Ciao,
  Oliver
Previous: Michal Suchánek
Message 5 of 5 in “"git overlay" - command for overlaying branches”
  1. Oliver BandelNov 24, 2023
  2. Michal SuchánekNov 24, 2023
  3. Oliver BandelNov 24, 2023
  4. Michal SuchánekNov 25, 2023
  5. Oliver BandelDec 1, 2023

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.