(ode$linger
(ode$linger
Member since: Oct 2005
Recent posts
| Post | When |
|---|---|
| they're just directories, and trunk is just a name. By convention though there is usually one. If |
Posted in
Multiple Trunks instead of Single Trunk
|
| It's something subversion can't do yet. It doesn't really do a good job with moves and renames. |
Posted in
"Skipped missing target" -- why?
|
| You could. The only problem is that the current diff format is not capable of describing everything |
Posted in
Vendor branches question
|
| Yes, if you have SSH access to your server, then it's very simple just to update the working copy on | |
| If you're on unix, symbolic links could solve your problem. |
Posted in
Some Advice on How to Mimic Sharing for This Project
|
| Yes, you should have two branches (at least). One for the fixes and one for the new work. You woul | |
| Sounds like what you're asking is what is most common. I don't think there's any way to know what's |
Posted in
Set up of directory
|
| It's also possible that many people don't have an answer because they're still on 1.4. The answer I |
Posted in
Cleaning up weird mergeinfo after unconventional merging
|
| If one project is dependent on another, consider branching the dependent branch off the other, and n |
Posted in
managing many small tasks
|
| Re: Merge: how to replace an old working copy with trunk No, it's very possible and easy (if I'm ... |
Posted in
Merge: how to replace an old working copy with trunk
|