Michael Stapelberg <michael+deb...@stapelberg.de> writes: >> Interesting idea though with fetching/storing configuration files via a >> revision control system. I think it would be worthwhile investigating >> the use of branches to capture the differences between hosts. > I decided against that in the first place because the actual differences > between the hosts are so minimal (at least in my case) that they can be better > managed by source-ing the file in the zshrc or xsession for example. Just > putting the files into a host-specific folder reduces maintenance. If you know > a really easy solution to the following scenario, I’d be delighted to hear > about it, though: > - have one branch for each computer (let’s say i’d use 15 different ones) > - make a change i want to have on every computer > I would now commit it on the master-branch and then use git cherry-pick on > each other branch. Is there a better way? > TopGit[0] should be able to do this. Your (merge) history would become messy over time, though.
[0] http://repo.or.cz/w/topgit.git?a=blob;f=README -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
