[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Checkout every file as read-only; make some of them editable with a explicit command.

From: Esteban Bolanos <ebolanos_at_datatec-ec.com>
Date: 2004-11-16 21:13:07 CET

Kevin,

        Thanks for your comments. However, I think there's been confusion regarding
my post: originally, I wasn't talking about reserved (exclusive) checkouts,
but rather about a SVN mechanism that would duplicate CVS' read-only
checkouts and "cvs edit" command, which turns a particular file editable.
This operation is not exclusive; many users can "cvs edit" the same file in
their working copies.

        In the case I exposed, the purpose of checking out files in read-only mode
is to keep users from doing accidental changes in files they shouldn't
change and then commiting those changes without noticing; it is not about
obtaining exclusive locks on files. AFAIK, "cvs edit" is normally used when
working with watches, but this particular group of CVS users utilize it to
prevent accidental changes.

Greetings,
Esteban.

> -----Original Message-----
> From: Kevin Williams [mailto:kevin@bantamtech.com]
> Sent: Martes, 16 de Noviembre de 2004 14:54
> Cc: Subversion Users
> Subject: Re: Checkout every file as read-only; make some of them
> editable with a explicit command.
>
>
> Exclusive checkouts vs. merge behavior is one of those never ending
> discussions, like spaces vs. tabs, that is up to personal
> interpretation. I believe the Subversion authors don't like exclusive
> checkouts. Therefore, I believe this feature is only being added due to
> popular demand. They are in no hurry because there's also a number of
> people who don't need it.
>
> Until Subversion offers both ways of doing things, it may help anyone
> wishing for exclusive checkouts to try things "the Subversion way".
> Create a test repository, have a few users use it, purposefully create
> some conflicts, and follow the documentation to resolve the conflict. If
> a majority finds they can work faster (assuming conflicts are rare if
> project work is divided among developers) than if they run into
> exclusive checkout restrictions, then the problem is solved.
>
> It's a matter of personal taste. IMHO, it's like trying a food you've
> never had - it's impolite to not at least TRY it before deciding it's bad.
>
> Hope that helps,
>
> Kevin
>
> Petri Varsa wrote:
> > Version 1.2 is supposed to have this feature. I don't know when 1.2 is
> > supposed to be released, but the subversion roadmap mentions this
> > feature.
> >
> > http://subversion.tigris.org/roadmap.html
> >
> > -petri
> >
> > -----Original Message-----
> > From: Esteban Bolanos [mailto:ebolanos@datatec-ec.com]
> > Sent: November 16, 2004 10:53 AM
> > To: Subversion Users
> > Subject: Checkout every file as read-only; make some of them editable
> > with a explicit command.
> >
> > Hello,
> >
> > Is there a way to checkout files in read-only mode ("protected"
> > files), and
> > then enable the edition on just the files that one wants to work with?
> >
> > Some CVS users who are considering migrating to SVN asked me
> > this, because
> > that's a "feature" that they use frequently. I don't know much about
> > CVS,
> > but they tell me that, with it, it's possible to checkout files in
> > protected
> > mode and then issue a "cvs edit" command only on the files they intend
> > to
> > change, in order to prevent accidental changes. All that I know about
> > "cvs
> > edit" is that it is normally used in the context of watches; howewer,
> > they
> > don't use it for change notification, but rather just as a protection
> > mechanism.
> >
> > How could one achieve a similiar effect in SVN?
> >
> > Thanks,
> > Esteban.
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.795 / Virus Database: 539 - Release Date: 12/11/2004
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.795 / Virus Database: 539 - Release Date: 12/11/2004
>

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.795 / Virus Database: 539 - Release Date: 12/11/2004
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 16 21:15:51 2004

This is an archived mail posted to the Subversion Users mailing list.