From: Jens Seidel (jensseidel_at_[hidden])
Date: 2008-05-24 13:12:32
On Sat, May 24, 2008 at 04:32:36PM +0100, James Sharpe wrote:
> 2008/5/24 Jens Seidel <jensseidel_at_[hidden]>:
> >> plays havoc with working copies if a new branch with the previous name
> >> is then created again as subversion doesn't detect the move. This is
> > I think this has changed recently (ehm, I mean in 1.5):
> > * 'svn update' now sometimes copies or moves local files, for efficiency
> Does it work in this case?:
Hard to say as it requires a network sniffer on my fast LAN (I don't
notice any delay) so I don't care. Nevertheless I assume it.
> svn co http://foo/branch/release
> (some one else moves branch release to be release_last then creates a
> new branch release)
> svn up
> It certainly didn't last I tried it with 1.4. (It's also unclear what
> the expected behaviour should be: should svn up now retrieve
> release_last or release?)
Calling "svn up" from the current directory would update all
subdirectories. So release/ would be deleted and release_last/ created.
After this the new release/ is fetched.
If "svn up" is called from inside release/ nothing would happen, as the
content of this directory (with URL .../release_last_at_HEAD) was not
It's really trivial.
You may find renaming obscure but I was forced to rename my trunk/
already 2 or 3 times because my colleagues work against Subversion
and provide from time to time a new "current" tree (handled
independently of Subversion, but some patches from it merged in) based
on a very outdated branch. I try to educate and think I won the battle
recently, lets see ...
It worked well in Subversion (apart from the fact that I found a few
bugs in it this way such as the "checksum mismatch" bug which is
already fixed after I was able to reproduce it with a small example).
> I don't consider it as static, but this isn't the only gripe I have
> against subversion. I've worked with subversion extensively and have
> now moved all my personal code projects to use git as I find it far
> more usable (the only downside I currently see in distributed systems
Do you have experiences with git-svn? Maybe by importing Boost's code?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk