3 ms·
> “origin” is also just the default name for the cloned remote I don't have a central dotfiles repo anymore (that I would always to forget to push to); I have
by lloeki 1y ago
> “origin” is also just the default name for the cloned remote
I don't have a central dotfiles repo anymore (that I would always to forget to push to); I have SSH access to my devices - via tailscale - anyway so I'm doing
git remote add $hostname $hostname:.config
and can cd ~/.config && git fetch/pull/rebase $hostname anytime from anywhere.
I've been considering a bare repo + setting $GITDIR (e.g via direnv) but somehow the dead simple simplicity has trumped the lack of push ability
- xk3 1y agoWhat's the benefit of this compared to rsync or scp $hostname:.config/<TAB>? I put my whole home folder in git and that has its benefits (being able to see changes to files as they happen) but if I'm just copying a file or two of config I'll just cat or scp it--introducing git seems needlessly complex if the branches are divergent
- lloeki 1y ago> just a file or two I don't have to remember which to copy > rsync or scp I don't have to remember which is most recent, nir even assume that "most recent" is a thing (i.e nonlinear) It's all just: - a git fetch --all away to get - a git log --oneline --decorate --graph --all to find out who's where and when - diff and whatchanged for contents if needed - a cherry-pick / rebase away to get what I want, complete with automatic conflict resolution I can also have local experiments in local topic branches, things I want to try out but not necessarily commit to across all of my machines yet.