Hi Brane
Thanks for responding.
How about svn merging between working paths if the paths have spaces ?
eg
svn merge -c 12345 src/path to/Roaming Apple.txt /src/another path/Roaming
Apple.txt
Thanks once again.
On Tue, Jul 7, 2015 at 11:14 AM, Branko Čibej wrote:
> On 07.07.2015 19:58,
Hi All
We have SVN 1.6.
We like to perform a svn merge on a file where its filename has spaces.
eg
Roaming Apple.txt
Is this syntax correct below to svn merge to a working copy ?
If not, what should it be ?
svn merge -c 12345 "https://mytext.abb.com/app/path/to/Roaming Apple.txt" .
using quotes
Hi All
We like to block any code merges from branch A to branch B when someone
makes changes to certain folders in branch A.
In SVN, we learn that we could block using --record-only on branch B with
revision number from branch A.
How can we block based on branch A paths ?
We ask because we like
Hi All
We have a few revision numbers on trunk that we like to block but they are
not in consecutive order - i.e. rev numbers 1,5,8,10,11
We like to merge from trunk to a branch but would like to block them on the
branch.
What's the correct syntax for svn merge --record-only ?
Is it
svn merge -
Hi All
Are there side effects from applying the same svn merge --record-only on
the same revision number and a new commit each time it is applied ?
Would there be issues with SVN mergeinfo and/or SVN in general if one keeps
applying
svn merge --record-only on a revision number repeatedly and comm
Hi All
We use SVN 1.6
How do we perform a svn merge "revert" of a revision number that is
--record-only in linux shell before a svn commit ?
We perform
svn merge --record-only -c 1234 http://testsomething.com
We like to revert that step.
Thank you
Sincerely
Hi All
Would there be issues with SVN mergeinfo and/or SVN in general if one keeps
applying
svn merge --record-only on a revision number repeatedly and commit in a
svn merge --record-only followed by commit followed by svn merge
--record-only followed by commit and the next cycle begins ? It's not
Hi All
We use SVN 1.6
We like to perform code merging between branches and we are in a dilemma
situation.
Branch A exists
Folks making code changes on Branch A
Branch B created from branch A
Folks making code changes on both branches A and B
Branch A sync code merging to Branch B
After some time
Hi All
We like to reintegrate from bracnh to trunk and for unclear reasons some
files are touched that we dont want to get into the trunk so that seems to
indicate that the server thinks the password is correct, but there's some
other error going on
if we do a few reverts of a few files and direc