First, please forgive me if this is the wrong place for this. The mailing
list description says "The main mailing list for subversion discussion. High
traffic. Everyone welcome", so here I am. If this is the wrong place please
point me in the right direction.
Second, let me say that I really like Subversion! I have been keeping my
eye on it for a while now and things it appears that things are far enough
along that I might be able to use it for my revision control needs. Thanks
for all the hard work.
On to questions/defects/comments:
* I have had problems doing a revert (svn revert) on a directory after
having added sub-directories and files (svn add). This of course really
screws up any merges that I attempt and I end up having to manually clean
things up. I seem to remember that a defect might have been entered about
this but I can't seem to find it again.
* As a user I find it very annoying that a check out (svn co) into a new
working directory leaves all files with the current date time stamp. As a
contractor I often have to merge files in from customers source repositories
in my local repository I use for their work. To do this I do a fresh check
out (svn co) from Subversion, then do the equivalent of an update (most
often a 'get') from their repository over the top of my working directory.
However, because I have done this subversion now thinks that most files are
up-to-date because the 'get' sets the timestamps of files to a date in the
past, usually the last date it was edited. This leaves me with something of
a mess. As it is right now I am going to have to write a small python
script that will create a database of the current date time stamps of all
the files in a particular revision, check that in and then on a fresh
checkout run the script to reset all the date time stamps to their proper
values. Quite the hack. Frankly, there may be some better way to handle
this situation that I am simply not aware of. If so please point me in the
right direction as I REALLY don't want to do it this way but the other
benefits of subversion are just too good to ignore.
* I work on the windows platform and so far have been running Subversion
locally. Having to move back to the drive the repository is not because svn
does not understand file:// commands issued for a repository not on the
current drive is a bit of a pain. Is this going to be addressed by 1.0?
Please understand this is not a huge issue, just a question.
* I just don't get how to merge changes made on the trunk into a 'branch'
used as a private workspace. It may have been I come from the PVCS world
and frankly to put it nicely I find it one of, if not the most, frustrating
pieces of software I have ever had the opportunity to use. However, coming
from that background also limits my experience's with some of Subversions
more sophisticated features. I have read the Subversion book and have spent
some time using it on a test repository but I still find the explanation of
it lacking and I am sorry that I can't be more clear than that. Perhaps an
-trunk check in at revision 7
-branch to create private workspace. This creates revision 8
- work continues on the trunk while I am doing lots of work in private
workspace. Repository revision is now at 25
-I decide that I need to merge in the changes from the trunk. Now do I
specify revision 7 from pre branch or 8 where the branch was created? And
what if I know that I only want to merge in the changes from revision 9 -12
and 14-17. Revision 13 was a trunk change that I just don't want at this
time and I also don't want other trunk changes after revision 17. And how
do I merge changes from another branch into my branch, so I can pickup SOME
of the work my co-worker. I guess just a few more examples would be nice.
If there are some available just point me in the right direction.
Thanks a lot for your time and patience
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri May 2 16:45:49 2003
This is an archived mail posted to the Subversion Dev