trying to decide whether the following statement is true:

When you `git checkout` a branch...
git remembers that it's checked out, UNTIL...
you explicitly `git checkout` or `git switch` to something else

is there a counterexample? so far I have:

* `git rebase` and `git bisect` store the branch and restore it when they're done
* `git reset` doesn't switch branches
* you could `git symbolic-ref` but that's just weird

@b0rk You git submodule update from a project that contains that repo as a submodule.

@b0rk @madewokherd I have various mental models, guidelines and scripts to help me deal with git.

For git submodule the guideline is very simple: don't.

@chx @b0rk I have things that I avoid instead of learning (git pull is the main one), but I have been forced to learn submodules for work, and I have use cases where they seem to be the best solution.

@madewokherd @b0rk I am doing enough insane things with git (the latest is supported by incron of all things!) but submodules is where I draw the line. I am so happy I have enough control to avoid them.

Follow

@chx Hi, while it's cool that you have a project you're enthusiastic about, I don't actually know you and as such, I'm not particularly interested in what you're doing. I barely care enough to google what "incron" even is. I would prefer that you not try to engage me in random topics in replies. (As I see it, the norm is to introduce topics on your own timeline and in conversations with people you know.)

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!