On Nov 20, 2007, at 02:55, p karthik wrote:
> Even I don't think adding $Id$ would break the application in any
> way. I know that we are just adding the version information to the
> file.
> But the thing is, as we are now in a end to end testing phase,
> which involves a lot of resources, we would be needing patches for
> all the defect fixes which arise during the testing.
>
> As we are against the "cherry-picking" concept, which means we
> don't take only some files from Subversion to build a patch,
> implies we need to take each and every file for the deployment if
> it has changed for any reason. If we modify the files by adding $Id
> $ in to the file those require a commit and consequently they would
> be going as a patch which would have huge number of files, and
> which is not intended as a deployment downtime per se.
>
> So the only way I have is to add this $Id$ with out actually
> commiting, but the files should be having $Id$ in Subversion.
Well, Subversion doesn't offer you a way to do this. If you want "$Id
$" (or anything else) in a file, you're going to have to modify the
file in a working copy and commit it.
If you don't want a lot of changes like this in the repository right
now, make the changes at a later time when it's more acceptable.
If there is no such time, then add the $Id$ line at a time when
you're making other changes to that particular file anyway. Files you
do not change will not have the $Id$ line.
If you would like to enforce this requirement, you can write a pre-
commit script which rejects the commit of any file that doesn't have
the $Id$ line.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 20 18:22:54 2007