[Chicago-talk] Question of preference
jason at multiply.org
Thu Jan 3 21:19:49 PST 2008
if you share your repo with a team and check in broken code you are a
jerk. If you want version control bring it into a local branch or use
something like svk or __INSERT FANCY NEW DISTRIBUTED VERSION CONTROL
TOOL DU JOUR HERE__ to help you out, but don't pollute a shared repo
with code that doesn't work.
if you use VCS for yourself then you can do whatever you feel best, obviously.
On Dec 30, 2007 4:31 PM, Steven Lembark <lembark at wrkhors.com> wrote:
> >> SVN supports this via pre-commit checks; problem
> >> is that you usually want people checking in code
> >> regularly to avoid loss of work. Catch: if you
> >> can only check in working code then you cannot
> >> make periodic checkins to make sure you don't
> >> loose work.
> > you don't want to lose code *that works* not just any random code.
> > SVN != RSYNC for a developer sandbox. :)
> So if it takes you three weeks to finish some work
> you wouldn't want to make any partial commits? You
> would prefer not to have any option of working
> on the code at remote locations, or give anyone else
> working on the project with you any chance at all to
> see the in-process code? You also would want to be
> able to try any changes with the option of backing
> them out later to a sane re-start point if an idea
> didn't work, I suppose?
> I've found all of these helpful at various times.
> You might not want to put the code back into the
> main production branch the first day, but the ability
> to commit partially complete projects is a powerful
> feature of SVN (and CVS).
> Steven Lembark 85-09 90th St.
> Workhorse Computing Woodhaven, NY, 11421
> lembark at wrkhors.com +1 888 359 3508
> Chicago-talk mailing list
> Chicago-talk at pm.org
More information about the Chicago-talk