Post 316526 by acrylicjam@mastodon.sdf.org
(DIR) More posts by acrylicjam@mastodon.sdf.org
(DIR) Post #299629 by acrylicjam@mastodon.sdf.org
2018-09-30T15:10:08Z
0 likes, 0 repeats
Is this a bad idea? I'm hosting a GIT Repo on a home server for dotfiles across my machines (two laptops, the server itself (in case config files change) and a second server). Previously I was syncing each device with a separate repo (important as some have v.distinct config files, e.g. .xinitrc) but now I've switched to just using branches off one repo. Is this a bad idea?#git #archlinux #RPI #RasPi
(DIR) Post #299630 by acrylicjam@mastodon.sdf.org
2018-09-30T15:10:55Z
0 likes, 0 repeats
Extremely new to GIT so learning the etiquette/best practice as I go. But rn I'm thinking: as long as I just make sure I'm using the correct branch, and continue these branches indefinitely, this is fine, right?
(DIR) Post #299631 by tomasino@mastodon.sdf.org
2018-09-30T15:49:05Z
0 likes, 0 repeats
@acrylicjam unless you're collaborating with others there's no right or wrong. If it's working for you your good to go
(DIR) Post #299780 by acrylicjam@mastodon.sdf.org
2018-09-30T16:02:30Z
0 likes, 0 repeats
@tomasino zero collaboration: these are only ever my machines. I just wanted to check in case I perhaps didn't understand branches. I mean I understand trees and from any tree I've ever seen I've never seen a branch return to the centre of the tree (which would be the only fear here) so based on that logic, if Git follows it, I believe i'm fine.I think I was just looking for external assurance (such as yours; so thank you!)
(DIR) Post #299860 by tomasino@mastodon.sdf.org
2018-09-30T16:08:40Z
0 likes, 0 repeats
@acrylicjam there are a ton of models for using branches and merging them back together. git flow, GitHub style, and pretty much a different pattern for every shop out there. If you want to maintain branches for machines independent of one another, that sounds great. You can cherry-pick commits between them for things you want in multiple places, and easily create new branches. I think you've got a nice system in place
(DIR) Post #299894 by acrylicjam@mastodon.sdf.org
2018-09-30T16:10:44Z
0 likes, 0 repeats
@tomasino Thanks so much for the reassurance! I'm glad to finally be using git. The more I look into it it does seem fascinating, particularly considered within its own historic context and the *need* for it to develop when it did as a VCS. Would quite like to master it in future.
(DIR) Post #299931 by tomasino@mastodon.sdf.org
2018-09-30T16:12:08Z
0 likes, 0 repeats
@acrylicjam the git book scm (https://git-scm.com/book/en/v2) is really solid. Everything else comes with time and practice
(DIR) Post #300120 by acrylicjam@mastodon.sdf.org
2018-09-30T16:24:48Z
0 likes, 0 repeats
@tomasino I downloaded that the other week. Looks like an epic undertaking in itself, but yeah maybe I'll see if I can crack on into it:)
(DIR) Post #300156 by tomasino@mastodon.sdf.org
2018-09-30T16:27:06Z
0 likes, 0 repeats
@acrylicjam when new developers without git experience join my team I have them read The first 4 chapters as a baseline. It just takes a few hours. If you're already doing things it'll be mostly review, but great to fill in knowledge gaps.
(DIR) Post #316526 by acrylicjam@mastodon.sdf.org
2018-10-01T17:31:19Z
0 likes, 0 repeats
@tomasino reading now (at least the first 4 chapters!)