> > Create local copy of trunk, make changes,
>
> ... fuck up, undo last local commit ... wait - can't do this in SVN!
oh come on... every SCM is transactional (ok, old goo boxes aren't
but who uses those?), and once committed, it's there. Rolling back isn't
hard though, and yes also in svn not hard :)
> > run tests, create
> > patch,
> > send patch. patch gets applied to trunk, used does update on local
> > copy, like everyone else and they all now get the patch. I don't see
> > why history is a problem for the _trunk_ using people. Sure, if you
> > create branches with code obtained from others OUTSIDE the trunk, then
> > it's problematic, but NH is always developed on the trunk, so that's
> > not really a problem IMHO.
>
> What if you're maintaining your own branch with your own modifications?
What
> if you want to backport one single bugfix that's just so important to you
to
> a stable release? DVCS makes all of that so much easier.
good point.
> > It however ended up
> > in a
> > debate whether dvcs is better or not. Who gives a ****, really. The
> > real pain is in writing the complex code to fix the harder problems,
> > not whether some scm is capable of easy merging or creating a patch.
>
> For a few lines of code, agreed. If a patch takes a while to write and/or
> involves several people, SVN just fails to deliver the most basic SCM
> functionality. You'd need to create a branch, assign rights... and still
> merging would suck (affects applying the patch after other updates or
> porting it to another branch). DVCS lets me just keep things in sync.
a dev branch with more than 1 person, and which is merged into main
trunk... agreed. Is NH set up that way btw? Feature teams? IMHO it's pure
individual oriented.
> In the context of NH, I still fail to see the problems that would be
> specific to DVCS.
the only problem which could pop up is code merged in local repos
pulled from local repos which is then merged to main trunk. You know, the
problem I mentioned ;). As apparently people here aren't that strict, it's
not something to worry about, right?
FB
