You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by we...@tigris.org on 2009/05/12 22:39:48 UTC
user can only update from head revision
Hi all,
Its possible deny the svn update on prev revisions? in the word, the
user can update/checkout only the HEAD version, neither another one !
thanks!
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2222687
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: user can only update from head revision
Posted by David Weintraub <qa...@gmail.com>.
I think as others have pointed out, you can't force people to only
check out from the HEAD.
However, Subversion won't allow a user to commit unless the commit is
at the HEAD of a branch. If I checkout from revision 1234, and the
HEAD revision is 2000, I can't commit any changes unless it so happens
that the file at revision 1234 just happens to be the head of the
revision.
If you need to revert back to an earlier revision, you need to do a merge.
The default behavior of Subversion is to always checkout from the
latest revision of that branch or trunk. It is assumed that if a
developer specifies the actual revision, then there's a good reason
why the developer is doing this.
One of the things I've learned from my two decades of doing builds and
releases is that we have to treat our fellow employees as
professionals who are just as interested in doing a good job as we
are. If you cannot treat a particular employee that way, then that
employee should find another line of work.
Other employees resent when you try to control what they are doing
because you implicitly don't trust them. They'll grow to hate the
tools. They'll grow to hate the process. They'll look at you not as a
fellow player whose concerned about getting out a quality product, but
as a impediment for them doing their job.
So, you need to ask yourself why must you prevent employees from
checking out earlier revisions of a module. Is it some "best practice"
idea you have, or have developers messed up the release process
because they did this before?
If it is the latter, you may need to find out why developers tried
doing this and how you can change the development process to help
developers do what they need.
On Tue, May 12, 2009 at 6:39 PM, <we...@tigris.org> wrote:
> Hi all,
>
> Its possible deny the svn update on prev revisions? in the word, the
> user can update/checkout only the HEAD version, neither another one !
>
> thanks!
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2222687
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
>
--
David Weintraub
qazwart@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2238988
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: user can only update from head revision
Posted by Stephen Connolly <st...@gmail.com>.
2009/5/13 Ryan Schmidt <su...@ryandesign.com>
> On May 12, 2009, at 19:25, Andy Levy wrote:
>
> > On Tue, May 12, 2009 at 18:39, wrote:
> >
> >> Its possible deny the svn update on prev revisions? in the word, the
> >> user can update/checkout only the HEAD version, neither another one !
> >
> > Both svn co and svn up accept the -r option to specify what version to
> > check out/update to.
>
> Yes, and I believe he wants to prevent users from being able to do
> that, and allow them only to checkout and update the HEAD revision.
> AFAIK there isn't a built-in way to do that. It might be possible to
> add some Apache rules, that is if you're serving the repository with
> Apache, and if you can figure out the internal format of URLs
> Subversion uses. You may be able to deny access to URLs of old
> revisions or something. But I don't recall anything like this having
> been mentioned on the list before, so you're probably on your own. As
> someone else asked, it would be good to know why you want to do this.
>
Of course such rules would make it impossible to roll back changes... and if
poorly implemented could make it impossible to work with branches, etc
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2228044
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe@subversion.tigris.org].
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2230593
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: user can only update from head revision
Posted by Ryan Schmidt <su...@ryandesign.com>.
On May 12, 2009, at 19:25, Andy Levy wrote:
> On Tue, May 12, 2009 at 18:39, wrote:
>
>> Its possible deny the svn update on prev revisions? in the word, the
>> user can update/checkout only the HEAD version, neither another one !
>
> Both svn co and svn up accept the -r option to specify what version to
> check out/update to.
Yes, and I believe he wants to prevent users from being able to do
that, and allow them only to checkout and update the HEAD revision.
AFAIK there isn't a built-in way to do that. It might be possible to
add some Apache rules, that is if you're serving the repository with
Apache, and if you can figure out the internal format of URLs
Subversion uses. You may be able to deny access to URLs of old
revisions or something. But I don't recall anything like this having
been mentioned on the list before, so you're probably on your own. As
someone else asked, it would be good to know why you want to do this.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2228044
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: user can only update from head revision
Posted by Andy Levy <an...@gmail.com>.
On Tue, May 12, 2009 at 18:39, <we...@tigris.org> wrote:
> Hi all,
>
> Its possible deny the svn update on prev revisions? in the word, the
> user can update/checkout only the HEAD version, neither another one !
Both svn co and svn up accept the -r option to specify what version to
check out/update to.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2224546
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: user can only update from head revision
Posted by Tyler Roscoe <ty...@cryptio.net>.
On Tue, May 12, 2009 at 03:39:48PM -0700, webpost@tigris.org wrote:
> Its possible deny the svn update on prev revisions? in the word, the
> user can update/checkout only the HEAD version, neither another one !
Why do you want to do this? What are you trying to accomplish?
tyler