At the moment I do reject the entire commit, however, this is extreme.
Say a developer tries to commit 100+ files, carefully selecting these
files from a list of several other files. However, one of the files
selected is a rogue file and the entire commit is rejected because of
one file.
QUOTE
Don't modify an in-progress transaction, especially in the manner
you're describing. If you do so, the committer's working copy will
instantly be out of sync with the repository.
UNQUOTE
When you mention out of sync, does this mean that the working copy is
corrupted or is it out of sync similar to when the development is
actually being carried out. I was hoping that when the user is informed
with a list of rogue files that were not committed the first time, the
user can modify those files and re-commit them to the repository there
by syncing the working copy with the repository.
-----Original Message-----
From: Andy Levy [mailto:andy.levy@gmail.com]
Sent: Tuesday, December 12, 2006 10:08 AM
To: Aliasgar Ganiji
Cc: users@subversion.tigris.org
Subject: Re: pre-commit transaction modification - remove files
On 12/12/06, Aliasgar Ganiji <Aliasgar@epicsystems.com> wrote:
>
>
>
> I have a need to remove files from the pre-commit transaction such
that
> those files are not committed. However, the commit should continue
for the
> rest of the files. Is this possible?
Don't modify an in-progress transaction, especially in the manner
you're describing. If you do so, the committer's working copy will
instantly be out of sync with the repository.
If you don't want certain files committed, check for them in the
pre-commit and just reject the whole commit with an error message
explaining why.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 12 17:31:42 2006