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

Re: Re: Regarding issue in SVN

From: Ben Fritz <fritzophrenic_at_gmail.com>
Date: Thu, 29 Jan 2015 09:39:43 -0600

On Thu, Jan 29, 2015 at 9:23 AM, Asheesh Agrawal
<asheesh.agrawal_at_mpowersoft.com> wrote:
> Dear Ben Fritz, Thanks for your kind reply.I am extracting files using
> version log history and then exporting the required files.Please find
> the screenshot attached in this reply for your kind confirmation. Well
> I do not have conceptual misunderstanding of SVN :), Test1.txt file
> have 3 total revision versions i.e. 45,46,47 and Test2.txt file has
> only revision verison i.e. 49 while one verison is for folder i.e.
> 44.The same I have mentioned during commit message. Now when I am
> exporting versions 44,45,46(Test1 file) and 49(Test2 file) at a time
> on my desk then after exporting I could see in Test1 file the changes
> for revision version 47 as well which should not be. If version 49
> would be related to Test1 file then I could understand that it will
> contain the changes for version 47 in by default. I hope issue is
> clear now. Please go through the screenshots attached on 28Jan2015
> post.

The problem is, that you have selected revision 49 as your latest
revision. As I mentioned, *all* files in your repository are contained
in *every* revision (except where files have been deleted or do not exist
yet) so naturally exporting files from revision 49 will contain all
previous changes.

Files don't have revisions. Revisions have files at a certain state.

Don't think of revisions as versions of a file. Think of them as the
evolution of your entire project with the passage of time.

To do what you are attempting, you will need to select only the one
revision you wish to export, for each file.

However, you should really re-think your deployment and development
method, if you are cherry-picking individual revisions of individual
files for release. Each release should be of an entire revision or it
will be very difficult to track in the future. If you must, then feel
free to create a new branch and revert any changes you don't want to
release, but you should not be releasing anything you can't recreate
with a simple update to a single revision or tag.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-01-29 16:40:10 CET

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

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