Cayetano Santos <[email protected]> writes:
Two I’m aware of. First:
git rebase HEAD pulls/pr/1855
This replays on top of HEAD a pr, keeping your precious .go
files
intact.
Andreas Enge <[email protected]> writes:
Am Thu, Oct 16, 2025 at 04:49:50PM +0200 schrieb Cayetano
Santos:
Second, using git worktrees, when you work of something
different so
frequently that it is worth to build new .go files once.
To make this precise, as far as I understood:
For instance, to work on kde-team in addition to the master
branch, run
git worktree add -b kde-team kde-team kde-team
to create the subdirectory kde-team and to check out the
kde-team branch
into it (I am not sure if there is a version with fewer
"kde-team"
typing, everything else I tried did... something else from what
I wanted).
In the subdirectory, "git log", "git pull" etc. now refer to
this branch
only. The price to pay is that you need to ./bootstrap,
./configure, make
a second time there. And you increase the size by the
corresponding .go
files.
Thanks for the ideas. In my case the .go files are still there,
but guile has decided that they're stale, which suggests that `git
switch` might be touching source files in the workspace even when
they haven't really changed between branches. So I guess that the
essence of these suggestions might be that `git rebase` is less
prone to this behavior? I will have to experiment.
Cheers,
Jason
