On Thu, Mar 10, 2016 at 1:10 AM, Johan Corveleyn wrote:
> [ Please, if possible, use plain-text on this mailing list, and use
> bottom-posting (putting your reply at the bottom, or inline to the
> thing you're replying to). More below ... ]
>
> On Wed, Mar 9, 2016 at 3:08 PM, wrote:
>> These fil
c: "users@subversion.apache.org"
Sent: Wednesday, March 9, 2016 7:10 PM
Subject: Re: Weird Behaviour: Files reverted that didn't show up in a status
--no-ignore
[ Please, if possible, use plain-text on this mailing list, and use
bottom-posting (putting your reply at the bottom, or
[ Please, if possible, use plain-text on this mailing list, and use
bottom-posting (putting your reply at the bottom, or inline to the
thing you're replying to). More below ... ]
On Wed, Mar 9, 2016 at 3:08 PM, wrote:
> These files were never changed in the first place, that's the weird part.
>
Re: Weird Behaviour: Files reverted that didn't show up in a status
--no-ignore
On Sat, Mar 5, 2016 at 12:50 AM, wrote:
> It was 1.8.14 client.
>
> It just said "Reverted " and the subsequent "svn status" made no
> mention of the .
Okay. I guess you cann
On Sat, Mar 5, 2016 at 12:50 AM, wrote:
> It was 1.8.14 client.
>
> It just said "Reverted " and the subsequent "svn status" made no
> mention of the .
Okay. I guess you cannot investigate anymore whether the content of
those files was really reverted (changed), or whether it was just some
unint
eird Behaviour: Files reverted that didn't show up in a status
--no-ignore
On Wed, Mar 2, 2016 at 9:53 PM, wrote:
> We are running VisualSVN 1.9.3 server on a Windows box and a user's
> workspace is on a Centos6.5 Linux box.
> He had just done a "svn update" and t
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: donderdag 3 maart 2016 09:30
> To: webster.br...@rogers.com
> Cc: users@subversion.apache.org
> Subject: Re: Weird Behaviour: Files reverted that didn't show up in a status
> --
&g
On Wed, Mar 2, 2016 at 9:53 PM, wrote:
> We are running VisualSVN 1.9.3 server on a Windows box and a user's
> workspace is on a Centos6.5 Linux box.
> He had just done a "svn update" and the build failed. No conflicts as far
> as I can tell. The "svn status" showed the build artifacts and his
