10/3 Is there a command in cvs that'll tell me what files I've
editted/changed from the original cvs update? \_ Use the -n flag.
I normally use cvs -n update. \_ Do you have to use CVS or can
you migrate to something else?
\_ Yeah, subversion is quite nice. I hated it at first, though
\_ How do you find out what files I've editted in svn?
\_ svn status -q
\_ Subversion has a lot of FUCKED concepts. Like how tags
and branches actually move the path to your files.
However compared to cvs, svn wins. \_ ??? The biggest
problems are:
1) lack of automated merge suppport (big improvements
planned for next version), and 2) 'move' is actually
'cp and rm' (don't know when this is expected
to change). \_ I'm not a revision control expert.
Why is move being a
cp and rm a bad thing? -dans \_ Heh. Work answers
all:
So a little while back I renamed some
branches. Seems pretty okay, right? Anyone
with a checked-out copy can just svn switch...
... except that svn considers the mv internally
to be svn cp + svn rm, so it has now forgotten
the revision history on that branch prior to
the svn mv. So if you, like me, do svn log
. --stop-on-copy to get a look at a glance at
what changes have been made since the branch
was cut, you can't. Q: Are there other things
that go wrong with svn mv? -dans \_ Branch.
Do a mv on a file. Edit file. Merge.
Pain happens. -aspo
\_ Use the -n flag. I normally use cvs -n update.
\_ Do you have to use CVS or can you migrate to something else?
\_ Yeah, subversion is quite nice. I hated it at first, though
\_ How do you find out what files I've editted in svn?
\_ svn status -q
\_ Subversion has a lot of FUCKED concepts. Like how tags
and branches actually move the path to your files. However
compared to cvs, svn wins.
\_ ??? The biggest problems are:
1) lack of automated merge suppport (big improvements
planned for next version), and
2) 'move' is actually 'cp and rm' (don't know when this is
expected to change).
\_ I'm not a revision control expert. Why is move being a
cp and rm a bad thing? -dans
\_ Heh. Work answers all:
So a little while back I renamed some branches. Seems
pretty okay, right? Anyone with a checked-out copy
can just svn switch...
... except that svn considers the mv internally to be
svn cp + svn rm, so it has now forgotten the revision
history on that branch prior to the svn mv. So if
you, like me, do svn log . --stop-on-copy to get a
look at a glance at what changes have been made since
the branch was cut, you can't.
Q: Are there other things that go wrong with svn mv?
-dans
\_ Branch. Do a mv on a file. Edit file. Merge.
Pain happens. -aspo |