On Tue, Jan 6, 2009 at 00:26, J. Bakshi <joydeep_at_infoservices.in> wrote:
> Srilakshmanan, Lakshman wrote:
>> Hi Bakshi,
>>
>> Think of the revision as an implicit tag. So every time you commit you
>> get a new tag created.
>>
>> The equivalent of revision per file in cvs does not exist in svn, but
>> with experience you will find that it is not important to have a
>> sequentially incrementing revision number for every file.
>>
>> What is important is the ability to trace the file to the last commit
>> (change) which is adequately provided in svn using the global revision
>> number.
>>
>
> Hello Andy and Lakshman,
>
> Thanks a lot for your explanation and response. The problem I am facing
> is really make me very nervous.
>
> Say there are total 3 projects in a repository. If you change any file
> in a particular project it actually changes the version of the
> repository. So I am in search for a way where it treats the project
> individually. Could you please enlighten me in this direction ?
3 options, in decreasing order of desirability (for me, anyway)
1) Don't get hung up on it and go forward
2) Separate repositories for each project
3) Use another VCS that meets your requirement
Received on 2009-01-06 12:55:16 CET