01:17 pm, 13 Dec 03
more arch
Just after I posted that last bit about arch, I realized how decentralized development is supposed to happen: independent branches that you occasionally merge. I was still thinking in the one-central-repository mindset and couldn't figure out how you mirrored stuff. But I'm still not sure where the repository belongs... :)
Colin Waters (of Rhythmbox, etc.) seems pretty sold on arch, too, and has a good summary of the basics. (But you really need to read the docs to make sense of a lot of it.)
Colin Waters (of Rhythmbox, etc.) seems pretty sold on arch, too, and has a good summary of the basics. (But you really need to read the docs to make sense of a lot of it.)
What do you mean by not being sure where the repository belongs, though? I always figured that with arch, you have an archive close to each place you hack, avoiding "the repository" entirely. That makes an after-work catchup session a merge from your work archive, and then you'd merge from your home archive the next day.