On 11/18/2011 7:24 AM, Csaba Raduly wrote:
On 11/18/11, Warren Young wrote:
How about "svn st -q ."?
That prints nothing if the folder is up to date.
Yes. And in the case the OP was concerned with, svn will complain
bitterly if the folder isn't versioned.
The worst side effect of doing
On 18/11/2011 14:24, Csaba Raduly wrote:
> On 11/18/11, Warren Young wrote:
>> On 11/17/2011 3:42 PM, Andrey Repin wrote:
[ one level of attribution lost here ]
$ ls -d .svn
>>> 1.7 working copy do not have .svn dirs in nested directories.
>>> http://subversion.apache.org/docs/release-note
On 11/18/11, Warren Young wrote:
> On 11/17/2011 3:42 PM, Andrey Repin wrote:
>>> On 11/16/2011 3:20 PM, Andrey Repin wrote:
it's a release you need to migrate your working copies
to 1.17 without checking them out anew.
>>
>>> Are you sure?
>>
>> As far as I understand the release n
Greetings, Warren Young!
>>> $ ls -d .svn
>>
>> 1.7 working copy do not have .svn dirs in nested directories.
>> http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng
> Sorry, I remembered that too late.
> How about "svn st -q ."?
I can't call it "at a glance".
--
WBR,
Andrey Repin (
On 11/17/2011 3:42 PM, Andrey Repin wrote:
On 11/16/2011 3:20 PM, Andrey Repin wrote:
it's a release you need to migrate your working copies
to 1.17 without checking them out anew.
Are you sure?
As far as I understand the release notes, you need to run "svn cleanup" with
earlier version, b
Greetings, Warren Young!
> On 11/16/2011 3:20 PM, Andrey Repin wrote:
>>
>> it's a release you need to migrate your working copies
>> to 1.17 without checking them out anew.
> Are you sure?
As far as I understand the release notes, you need to run "svn cleanup" with
earlier version, before runni
On 11/16/2011 3:20 PM, Andrey Repin wrote:
it's a release you need to migrate your working copies
to 1.17 without checking them out anew.
Are you sure?
After I got svn 1.7 via setup.exe, svn commands began failing in
preexisting checkout directories, telling me I needed to "svn upgrade"
the
Greetings, Jeremy Bopp!
> Thank you for confirming my memory regarding these format changes.
> Still, while it makes sense for the project to make backward
> incompatible changes at times, it still seems odd that the new clients
> wouldn't support using the working copies from at least 1 minor ver
Greetings, Andy Koppe!
> Can one use different svn clients on the same working copy, even if
> they are the same version?
You can even use them (literally) simultaneously. Subversion introduced an
appropriate locking mechanics to ensure as much as possible that all
transactions are atomic.
But, a
On 11/17/2011 10:09, Jon Clugston wrote:
> On Thu, Nov 17, 2011 at 10:37 AM, Jeremy Bopp wrote:
>> I want to think that they only change the working copy format when the
>> minor version changes, but I also think that they have done that with
>> every minor version transition since at least 1.4.
On 11/17/2011 05:12, Csaba Raduly wrote:
> On 11/17/11, Andy Koppe wrote:
>> Can one use different svn clients on the same working copy, even if
>> they are the same version? I've always been wary of that due to fear
>> of subtle differences in working copy format. Character encoding and
>> line e
On Thu, Nov 17, 2011 at 10:37 AM, Jeremy Bopp wrote:
> On 11/17/2011 01:39, Andrey Repin wrote:
>> Greetings, Jeremy Bopp!
>>
>>> All I really wanted to know was why it was important to hang back from the
>>> latest available version when getting the older one was less than trivial.
>>> Not using
On 11/17/2011 01:39, Andrey Repin wrote:
> Greetings, Jeremy Bopp!
>
>> All I really wanted to know was why it was important to hang back from the
>> latest available version when getting the older one was less than trivial.
>> Not using anything more than the command line for svn (infrequently at
On 11/17/11, Andy Koppe wrote:
> Can one use different svn clients on the same working copy, even if
> they are the same version? I've always been wary of that due to fear
> of subtle differences in working copy format. Character encoding and
> line endings are two possible trouble spots that come
On 16 November 2011 23:06, Jim Garrison wrote:
>> -Original Message-
>> On Behalf Of Jeremy Bopp
>> Sent: Wednesday, November 16, 2011 9:18 AM
>> Subject: Re: Rolling back to 1.6.x Subversion
>>
>> That whole process is going to be unsupported here th
Greetings, Jeremy Bopp!
> All I really wanted to know was why it was important to hang back from the
> latest available version when getting the older one was less than trivial.
> Not using anything more than the command line for svn (infrequently at that)
> made me forget how often that project c
Jim Garrison wrote:
>> -Original Message-
>> On Behalf Of Jeremy Bopp
>> Sent: Wednesday, November 16, 2011 9:18 AM
>> Subject: Re: Rolling back to 1.6.x Subversion
>>
>> That whole process is going to be unsupported here though, so is
>there
&g
> -Original Message-
> On Behalf Of Jeremy Bopp
> Sent: Wednesday, November 16, 2011 9:18 AM
> Subject: Re: Rolling back to 1.6.x Subversion
>
> That whole process is going to be unsupported here though, so is there
> some reason you must remain on such an old relea
On 11/16/2011 2:20 PM, Andrey Repin wrote:
> Greetings, Jeremy Bopp!
>
>>> I've accidentally updated Subversion to 1.7.x on Cygwin.
>>>
>>> Is there a way to get an older package of Subversion installed?
>
>> It looks like you'll need to check out the Cygwin Time Machine
>> (http://www.fruitbat.o
Greetings, Jeremy Bopp!
>> I've accidentally updated Subversion to 1.7.x on Cygwin.
>>
>> Is there a way to get an older package of Subversion installed?
> It looks like you'll need to check out the Cygwin Time Machine
> (http://www.fruitbat.org/Cygwin/index.html#cygwintimemachine) if you
> want
On 11/16/2011 7:18 AM, Jeremy Bopp wrote:
> On 11/15/2011 15:47, Sean LeBlanc wrote:
>> I've accidentally updated Subversion to 1.7.x on Cygwin.
>>
>> Is there a way to get an older package of Subversion installed?
>
> It looks like you'll need to check out the Cygwin Time Machine
> (http://www.fr
On 11/15/2011 15:47, Sean LeBlanc wrote:
> I've accidentally updated Subversion to 1.7.x on Cygwin.
>
> Is there a way to get an older package of Subversion installed?
It looks like you'll need to check out the Cygwin Time Machine
(http://www.fruitbat.org/Cygwin/index.html#cygwintimemachine) if y
I've accidentally updated Subversion to 1.7.x on Cygwin.
Is there a way to get an older package of Subversion installed?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
23 matches
Mail list logo
