[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: file by file revision

From: Hagerty, Joe <joeh_at_tentmakers.net>
Date: 2004-06-30 18:32:24 CEST

As a newb here, I wasn't sure if this were viable or not, but couldn't you use a user property to store the file revision number then simple search the database for the file revision number? Or a combination of the file revision number and the filename?

Also Ivan, is this an OpenSource Project you are working on? I may be able to donate some time to help since my boss has been bugging me to write one of these for a couple of months.

Joe Hagerty

-----Original Message-----
From: Ivan Horvath [mailto:i.horvath@alco.co.hu]
Sent: Wednesday, June 30, 2004 12:31 AM
To: Max Bowsher
Cc: users@subversion.tigris.org
Subject: Re: file by file revision

Dear Max,

yes, i can imagine that there are many advantage for this philosophy ...
here is what i need:
i would like to use a version control system to store documents, manage
histories, manage versions of docs in a document control system.
subversion is very nice for this, it has an own storage system, handle
permissions, web interface, etc, but small problem of handling version
numbers.
that means the document version number has to be managed by my
application, but how can i relate my version number to the real revision
number in subversion system?
if for instance a user wants to see the 2. version of the document, but
the last (actual) version is already 7. how i know that which revision i
should get from subversion history?

Max Bowsher wrote:

>Ivan Horvath wrote:
>
>
>>Dear All,
>>
>>i'm really new to use/implement subversion.
>>i installed on a windows 2k computer the system, and created a project,
>>and add some files, check out, commit, etc.
>>at the moment it looks like working for me, but i would like to get that
>>the system manage the revison number for each independent file/folder in
>>the project.
>>as i recognized the system increases the revision number per project,
>>that means if i add a new document (A) it receives the rev. no. 3. then
>>i add another document (B) receives revision 4. if i modify the document
>>A and commit it gets the revision 5.
>>is it possible to change this revision philosophy, that each file should
>>have an independent revision numbering, or not?
>>
>>
>
>No. Subversion's global revision number, whilst initially surprising to people with a background in cvs, is actually a great
>advantage once you get used to it.
>
>Have you ever tried to change the log message for a multi-file cvs commit?
>You have to look up the revision of each individual file, and apply the change to each. Not so with subversion.
>
>If you want to see the diff for a multi-file cvs commit, you have to find the date of the commit, and use a date range. Not so with
>subversion.
>
>Max.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>

-- 
Best Regards,
Iván Horváth
Chief Programmer
Alcatel NSD
PMS 2000 Product Team
H-1116, Budapest
Kondorfa u. 10.
Tel.: +36 1 209 9546
Fax.: +36 1 209 9599
Mobil: +36 30 257 0235
E-mail: i.horvath@alco.co.hu <mailto:i.horvath@alco.co.hu>
Check my Web Page <http://www.extra.hu/pillesoft>
Anyone who has never made a mistake has never tried anything new.
/Albert Einstein/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 30 18:48:12 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.