[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Branching with file-Protocol

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-06 21:45:02 CET

"Philipp Kordowich" <development@kordowich.net> wrote on 03/06/2006
03:39:43 PM:

> Hello Mark,
> thanks for your reply.
> On Sun, 5 Mar 2006 16:55:13 -0500
> Mark Phippard <markp@softlanding.com> wrote:
> >> Console:
> >> copy -rHEAD file:///D:/Subversion/Test/Test
> >> file:///D:/Subversion/Test/MyBranch
> >> But the new branch isn't created :-(
> >
> > If the Console said it succeeded, then it did. Does it
> >show a new
> > committed revision in the console? That output is
> >coming right out of
> > Subversion. Try showing the history for the MyBranch to
> >see if it shows
> > anything.
> The problem is that there's no success message in the
> console. Only the command appears - and nothing else. I
> checked twice (once with Subclipse and once with
> TortoiseSVN) that there's no branch created. Also gave
> this a check on a second plattform with the same result
> :-(

You are correct that it does not send a message, even when it is
succesful. The API must not send a notification, or maybe we just do not
have code to relay it.

That being said, when I tested this, it still works fine and the branch is
created. In my case, I know because I got a commit email.

Also, in testing I saw that when the command failed, it did issue messages
in the console. That is easy to verify. Enter a non-existant path as the
to URL, such as:



Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Mar 6 21:45:33 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.