"Johan Compagner" <jcompagner@gmail.com> wrote on 05/01/2006 11:17:41 AM:
> I don't know if this is a problem of svn itself or the eclipse plugin so
i
> ask it first here on the mailing list.
>
> When i am creating a patch it doesn't include new files. This is quite
> annoying if you ask me because now i have
> to make a patch and then also send all new files that are also part of
the
> patch as seperate files.
The patch is made using the svn diff command. It will only include new
files if you have done the Team -> Add option so that they are scheduled
to be added to version control. So if you want to include them in the
patch file you need to do that first.
> What i expect to happen if i have changes in my working copy of the
trunk
> and i want to branch this:
>
> I choose/create the branch folder
> i gives me an option which new files i also want to commit.
> It commits all the changed and the selected new files to that new
branch.
> The working copy is then all switched to the new branch and i don't have
any
> outgoing changes anymore (because everything is committed)
>
> Is this assumption wrong? Do i something that is not the svn way?
We use the svn copy command to create the branch based on the settings you
provide. A pseudo-command is logged in the Console. The best thing for
you to do would be to pursue your scenarion on the Subversion users@ list.
We have no ability to change the behavior of Subversion commands other
than what is exposed to us as command options.
Mark
_____________________________________________________________________________
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 May 1 18:00:27 2006