Re: [RFE] Update before commit

So it's only refused when a change happens to a file that you've changed? If
somebody changes a different file in the repository (but that still has
dependencies with the file you've changed), the code in the repository could
still break, right, even though the commit is accepted?

Any strategies for resolving such a case to ensure the repository contains a
fully functioning code base, or is this a usual part of the development
process?

(e.g. Any way of declaring a dependency of one file on another so that you
can't commit a file without first resolving conflicts not only in that file
itself, but in files you've declared that it depends on. If not, any
thoughts about this as a feature request?)

Greg Thomas wrote:
>
> On Wed, 14 Feb 2007 08:46:39 -0800 (PST), lightbulb432
> <veerukrishnan@hotmail.com> wrote:
>
>>Is an update before a commit necessary, or will Subversion tell you when a
>>repository has been updated since you checked out your working copy and
>>REQUIRE an update?
>
> An update is not generally required. However, if someone has committed
> something you are about to commit since you last updated, Subversion
> will refuse to commit - you'll have to do an update, resolve any
> conflicts that may arise, and then commit again.
>
> Greg
> --
> This post represents the views of the author and does
> not necessarily accurately represent the views of BT.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>

-- 
View this message in context: http://www.nabble.com/Update-before-commit-tf3228333.html#a8968969
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org