On Thu, Jun 23, 2011 at 5:01 PM, Geoff Hoffman <ghoff...@cardinalpath.com> wrote: > What I mean by that is, it may have ramifications down the road for *your > workflow* (I can't think of any obvious examples), but svn copy [from] [to] > works on any path, local or remote, as you would expect. > > On Thu, Jun 23, 2011 at 1:57 PM, Geoff Hoffman <ghoff...@cardinalpath.com> > wrote: >> >> Not in any general sense, no. >> >> On Thu, Jun 23, 2011 at 1:27 PM, Phil Pinkerton <pcpinker...@gmail.com> >> wrote: >>> >>> Any issues with creating a branch from a branch? no trunk and no merge >>> back to first branch ? >>> >>> >>> Phil
Oh, lord, top-posting. I just ran into a long rant about this on another list. One subtle booby trap that I *just* found out about, if you do something like this to internally "branch" your work and then delete the original material as part of a "how do I move this material to a better location in the source tree", rather than doing an "svn move", you break git-svn history of that internal "branch". Personally, I'm not put out by it: I see git-svn as a friendly portal for distributed work, not a primary access to subversion repository history, but it was profoundly irksome to people who believe that sacrosanct history is one of the whole points of a repository history, and I can understand that view.
