public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Rolling back to 1.6.x Subversion
Date: Fri, 18 Nov 2011 14:25:00 -0000	[thread overview]
Message-ID: <CAEhDDbDdJqoCk45DKBaB9dmzc7nJeaLBf_RTSzagKep4Mo53zg@mail.gmail.com> (raw)
In-Reply-To: <4EC5A338.9060302@etr-usa.com>

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 notes, you need to run "svn cleanup"
>> with
>> earlier version, before running "svn upgrade" with current one.
>
> I've done three successful tree upgrades with just an "svn upgrade".
>
> Perhaps the "cleanup" is only needed in uncommon cases?
>
>>> $ 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 ."?

That prints nothing if the folder is up to date.
Did you mean    "svn st -u ."   ?

-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2011-11-18 14:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 21:47 Sean LeBlanc
2011-11-16 15:18 ` Jeremy Bopp
2011-11-16 21:16   ` David Rothenberger
2011-11-16 22:35   ` Andrey Repin
2011-11-16 23:01     ` David Rothenberger
2011-11-17 19:06     ` Warren Young
2011-11-17 22:50       ` Andrey Repin
2011-11-18  0:14         ` Warren Young
2011-11-18  9:50           ` Andrey Repin
2011-11-18 14:25           ` Csaba Raduly [this message]
2011-11-18 17:23             ` Dave Korn
2011-11-19  9:30             ` Warren Young
2011-11-16 23:06 Jim Garrison
2011-11-17  0:53 ` Jeremy Bopp
2011-11-17  7:50   ` Andrey Repin
2011-11-17 15:37     ` Jeremy Bopp
2011-11-17 16:10       ` Jon Clugston
2011-11-17 16:47         ` Jeremy Bopp
2011-11-17 19:05           ` Andrey Repin
2011-11-17  9:10 ` Andy Koppe
2011-11-17 11:12   ` Csaba Raduly
2011-11-17 16:33     ` Jeremy Bopp
2011-11-17 19:05   ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEhDDbDdJqoCk45DKBaB9dmzc7nJeaLBf_RTSzagKep4Mo53zg@mail.gmail.com \
    --to=rcsaba@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).