On Fri, Aug 23, 2013 at 10:55:03PM +0200, Branko Čibej wrote:
> On 23.08.2013 21:34, Daniel Shahaf wrote:
> > 'svn list-branches' would work how?
>
> About the same as "svn mergeinfo"? Or how about a variant on "svn
> status" that also looks for that prperty? Frankly, I find this problem
> infinit
On Aug 23, 2013, at 13:31, Les Mikesell wrote:
> On Fri, Aug 23, 2013 at 1:09 PM, Edwin Castro wrote:
>
>>> I can't, off the top of my head, think of a scenario where it would be
>>> harmful to replace an unversioned directory with a versioned instance,
>>> leaving any unversioned local files th
Thanks for the quick replies. Looking forward to svn 1.8.3.
On Aug 23, 2013, at 11:56 AM, Ben Reser wrote:
> On Fri Aug 23 01:36:55 2013, Philip Martin wrote:
>> Stephane Odul writes:
>>
>>> I have a project that I need to fork (in the same repo):
>>> $ svn cp foo bar
>>> $ svn rm bar/trunk/s
> From: Jay Vee [mailto:jvsr...@gmail.com]
> Sent: Friday, August 23, 2013 5:09 PM
> To: users@subversion.apache.org
> Subject: how to simply : $svn update ?
>
> I do '$svn status'
> and get that I am at a certain revision
>
> Type 'svn help' for usage.
> cpu:/dir>svn update
> At revision 32933.
> I do '$svn status'
> and get that I am at a certain revision
>
> Type 'svn help' for usage.
> cpu:/dir>svn update
> At revision 32933.
>
> This leads me to believe that I am fully sync'd with the repo since it pulled
> nothing back.
>
> --- I do svn status and see something surprising
>
> cpu
I do '$svn status'
and get that I am at a certain revision
Type 'svn help' for usage.
cpu:/dir>svn update
At revision 32933.
This leads me to believe that I am fully sync'd with the repo since it
pulled nothing back.
--- I do svn status and see something surprising
cpu:/dir>svn status
? s
On Thu, Aug 22, 2013 at 4:15 PM, Laszlo Kishalmi wrote:
>>
> I'd propose a -b [--branch] option or extend the meaning of "^" sign for
> those commands which can work with URL-s. Extending ˇ would mean
> that when used as ^/ it means repository root and using it as ^[branch] then
> it would refer t
On 23.08.2013 21:34, Daniel Shahaf wrote:
> Branko Čibej wrote on Fri, Aug 23, 2013 at 16:37:47 +0200:
>> * svn mkdir --branch
>> Creates a new directory with the svn:branch property set, with an
>> empty value
>> Example: svn mkdir --branch http://host/repo/trunk
> 'svn list-branches
On Fri, Aug 23, 2013 at 4:09 PM, Maureen Barger wrote:
> I am currently planning an upgrade from SVN 1.5 (using svnserve and
> ssh tunnel) to SVN 1.8.1 fronted with Apache and webdav using AD for
> authNz.
> We have about 50 repos. I'll be moving from an older Ubuntu 8 install
> to Centos 6 x64.
Hi -
I am currently planning an upgrade from SVN 1.5 (using svnserve and
ssh tunnel) to SVN 1.8.1 fronted with Apache and webdav using AD for
authNz.
We have about 50 repos. I'll be moving from an older Ubuntu 8 install
to Centos 6 x64.
My thought was I could upgrade the SVN installation in place,
Branko Čibej wrote on Fri, Aug 23, 2013 at 16:37:47 +0200:
> * svn mkdir --branch
> Creates a new directory with the svn:branch property set, with an
> empty value
> Example: svn mkdir --branch http://host/repo/trunk
'svn list-branches' would work how?
On Fri Aug 23 01:36:55 2013, Philip Martin wrote:
> Stephane Odul writes:
>
>> I have a project that I need to fork (in the same repo):
>> $ svn cp foo bar
>> $ svn rm bar/trunk/some_dir
>> $ svn rm bar/trunk/some_file
>> $ emacs bart/trunk/other_files
>> $ svn ci
>> Segmentation fault: 11
>
> Is
On Fri, Aug 23, 2013 at 1:33 PM, Andrew Reedick
wrote:
>>
>> I can't, off the top of my head, think of a scenario where it would be
>> harmful to replace an unversioned directory with a versioned instance,
>> leaving any unversioned local files that happen to be there alone.
>> Other than maybe th
> -Original Message-
> From: Les Mikesell [mailto:lesmikes...@gmail.com]
> Sent: Friday, August 23, 2013 1:34 PM
> To: Edwin Castro
> Cc: Subversion
> Subject: Re: Switching
>
>
> I can't, off the top of my head, think of a scenario where it would be
> harmful to replace an unversioned
On Fri, Aug 23, 2013 at 1:09 PM, Edwin Castro <0ptikgh...@gmx.us> wrote:
>> I can't, off the top of my head, think of a scenario where it would be
>> harmful to replace an unversioned directory with a versioned instance,
>> leaving any unversioned local files that happen to be there alone.
>
> Lea
On 8/23/13 10:34 AM, Les Mikesell wrote:
> I can't, off the top of my head, think of a scenario where it would be
> harmful to replace an unversioned directory with a versioned instance,
> leaving any unversioned local files that happen to be there alone.
Leaving unversioned local files alone in a
On Fri, Aug 23, 2013 at 11:17 AM, Edwin Castro <0ptikgh...@gmx.us> wrote:
>>>
>> I don't buy the argument about different histories: the pre-existing
>> directory doesn't have a subversion history, so from svn's point of
>> view there is no conflict. What are the real, practical problems that
>> y
Good to know, thank you.
-Original Message-
From: Stefan Sperling [mailto:s...@elego.de]
Sent: Friday, August 23, 2013 12:50 PM
To: Edwin Castro
Cc: users@subversion.apache.org
Subject: Re: Switching
On Fri, Aug 23, 2013 at 09:24:52AM -0700, Edwin Castro wrote:
> I think the mailing lis
On Fri, Aug 23, 2013 at 09:24:52AM -0700, Edwin Castro wrote:
> I think the mailing list has already said the *best* way to use switch
> is to have a clean working copy (clean out all ignored and unversioned
> files which is admittedly inconvenient).
This won't help right now, but cleaning out suc
On 8/23/13 7:43 AM, John Maher wrote:
> The files in question are settings files (think config files) and
> intermediate compilet generated files. The settings files can be recreated
> at any time. If they are wrong the only thing affected is the development
> environment. The other files get
On 8/23/13 7:43 AM, John Maher wrote:
> The question is can I bring back my working directory from a failed switch
> (I'm talking undo, not resolve) so I can use the force option or must I
> always use the force option to be able to switch branches?
I think the mailing list has already said the
On 8/23/13 8:16 AM, Anders J. Munch wrote:
> Edwin Castro wrote:
>> I think the --force option is dangerous. Try it out but, in my opinion,
>> you should not use it.
> Why? Doesn't it perfectly solve the described problem?
The problem with --force, as the documentation points out, is that it
can m
Edwin Castro wrote:
> I think the --force option is dangerous. Try it out but, in my opinion,
> you should not use it.
Why? Doesn't it perfectly solve the described problem?
I had like so many others given up on switch, because cleaning up
working copies prior to the switch was annoying busywork,
I will try to explain one more time. The files in question are settings files
(think config files) and intermediate compilet generated files. The settings
files can be recreated at any time. If they are wrong the only thing affected
is the development environment. The other files get recreat
On 23.08.2013 16:06, Andrew Reedick wrote:
>
>> -Original Message-
>> From: Laszlo Kishalmi [mailto:lkisha...@ovi.com]
>> Sent: Thursday, August 22, 2013 5:15 PM
>> To: users@subversion.apache.org
>> Subject: Feature Req: sorthand urls for branches/tags in CLI
>>
>>
>>
>> Implementation ide
> -Original Message-
> From: Laszlo Kishalmi [mailto:lkisha...@ovi.com]
> Sent: Thursday, August 22, 2013 5:15 PM
> To: users@subversion.apache.org
> Subject: Feature Req: sorthand urls for branches/tags in CLI
>
>
>
> Implementation ideas:
> We put a specific property on project
Ben Reser wrote on Thu, Aug 22, 2013 at 22:18:49 -0700:
> bA=^/project1/branches/branchA
> svn merge $bA
That was also the argument against adding ^/, wasn't it?
The counter-argument is that "Make URL targets easier to input" is
a problem that every user of the cmdline client has (scripts include
On Fri, Aug 23, 2013 at 06:38:42PM +0530, Deepak Bhatia wrote:
> Hello,
>
> Ok I created a repository by giving the absolute path to the directory.
>
> svnadmin create --fs-type fsfs /home/deepak/public_html/svn2
>
> Then importing a directory is giving the error
>
> -bash-4.2$ svn import -m "N
How reliable is svn merge? What changes are that it fails with
success(instead of throwing a conflict it does a wrong merge)?
Hello,
Ok I created a repository by giving the absolute path to the directory.
svnadmin create --fs-type fsfs /home/deepak/public_html/svn2
Then importing a directory is giving the error
-bash-4.2$ svn import -m "New Import" . http://demo.voxomos.com/~deepak/svn2
svn: Repository moved permanent
On Fri, Aug 23, 2013 at 06:07:42PM +0530, Deepak Bhatia wrote:
> Hello,
>
> I am able to create the repository using
>
> svnadmin create --fs-type fsfs http://demo/~deepak/svn
'svnadmin create' requires a local path to a directory that
does not yet exist. It is supposed to be run on the SVN
Hello,
I am able to create the repository using
svnadmin create --fs-type fsfs http://demo/~deepak/svn
But the import of a directory is giving error
-bash-4.2$ svn import -m "New import" /home/deepak/keyword_spotter
http://localhost/~deepak/svn
svn: Repository moved permanently to 'http://d
On Thu, Aug 22, 2013 at 09:40:08AM -0400, James Hanley wrote:
> So other then tar-ing up the WC, there is no way to reproduce local changes
> like this on another system? I know the example given is fairly simple,
> but it could be very useful.
If the changeset you want to transfer between workin
On Wed, Aug 21, 2013 at 09:44:00AM -0600, Scott Chantry wrote:
> TortoiseSVN 1.8.1 windows x64. I opened up repo browser and after a long
> wait, this error popped up. I can't do anything with tortoisesvn1.8.1
I believe this will be fixed with Subversion 1.8.3 (ETA end of next week).
Please let u
Stephane Odul writes:
> I have a project that I need to fork (in the same repo):
> $ svn cp foo bar
> $ svn rm bar/trunk/some_dir
> $ svn rm bar/trunk/some_file
> $ emacs bart/trunk/other_files
> $ svn ci
> Segmentation fault: 11
Is that issue 4400?
http://subversion.tigris.org/issues/show_bug.c
35 matches
Mail list logo
