vlion: cut of the flammarion woodcut, colored (Default)
vlion ([personal profile] vlion) wrote in [site community profile] dw_dev 2012-05-04 03:09 pm (UTC)

Okay, I don't know what exor674 thinks real branching is, so I can't really speak to that charge. But I know that we use branches very successfully at $DAY_JOB, and they seem to be real branches keeping lines of development separate, which is their job. We also use ClearCase, which supports renamable/deleteable branches, and is a horrid terror in part due to that.

One key difference is hg design philosophy is ALL THE COMMITS ARE EVERYWHERE. You don't wind up with private commits after a pull/push in general. I.... don't see the problem with that in an environment where you want to ensure changes don't fall off the map. You *can* push-pull just one branch at a time if you so want, but I've never quite gotten the reasoning behind that.

You don't have *use* the other branches commits, after all. That's the point of working on a branch: you don't see other people's changes, even tho' they may be in the repository. I see no particular problem with 50-100 different branches/bookmarks.


With respect to namespace collisions: Yes, you could go out and name something the same branch. Why would you?

Most theoretical problems with DVCS don't wind up happening in real life; either they are too abtruse to happen, or they are socially worked around.

the fundamental question is: what do you WANT to have happen?

Post a comment in response:

If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org