This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: SVN for src (was Re: Binutils 2.18 prep)


Daniel Jacobowitz wrote:
Check out the trunk using "svn co -N" for non-recursive.  You will get
only the trunk - no subdirectories.  Unlike in CVS they will never
spontaneously appear after this point; "svn up" will only create new
directories when it updates through a revision in the repository that
created the directory.  Otherwise, it appears to assume that the
directory is deliberately missing if it is not mentioned in
.svn/entries.  However, an explicit "svn up gdb" in this case will
work!

Try a commit. I'm fairly sure that any subsequent check-outs within the working-copy are separate - you can't check-in changes to different directories simultaneously.


It will be perfectly adequate for building and diffing, of course.

Not everything is rosy.  "svn cp . $repo/branches/new-branch" will
copy the omitted directories, which is peculiar, so we would either
need people branching to get a hypothetical svn which didn't do that
or use a script to create branches.  But it's much less messy than
using externals would be.

What's wrong with creating a branch that contains everything? This is the natural way to work with svn - copies are not expensive. One can then check out modules on the branch in the same way as the trunk.


This does raise an interesting point: it would not be trivial to 'svn switch' to different branches. Not impossible, but not trivial.

Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]