Re: SVN BUG

2017-01-23 Thread Nico Kadel-Garcia
On Mon, Jan 23, 2017 at 6:20 AM, Swamy, Gagana Prabhu wrote: > Hi , > > > > Recently I faced the following issue: > > > > 1)My password that is used is “#anusuya2893#” > > 2)While checking out, I mistakenly used the password “#anusuya#” and it > worked fine without any error and the operation was

Re: SVN BUG

2017-01-23 Thread Ryan Schmidt
> On Jan 23, 2017, at 05:20, Swamy, Gagana Prabhu wrote: > > Hi , > > Recently I faced the following issue: > > 1)My password that is used is “#anusuya2893#” > 2)While checking out, I mistakenly used the password “#anusuya#” and it > worked fine without any error and the operation was succe

Re: svn bug or issue?

2016-09-05 Thread Stefan Hett
Hi Kai, On 9/4/2016 1:26 PM, Dorau, Kai wrote: Hi Guys, The communication between a svn server and client does’t work properly. Svn server version: 1.8.10 (r1615264) Svn client version: 1.8.10 (r1615264) OS on client: Debian 8.5 jessie 64bit OS on server: Debian 8.5 jessie 64bit Issue on c

Re: svn bug

2014-03-25 Thread Thorsten Schöning
Guten Tag Tomas Javurek, am Dienstag, 25. März 2014 um 16:52 schrieben Sie: > svn: Commit blocked by pre-commit hook (exit code 1) with > output: > Some parts of your commit look suspiciously like merge > conflict markers. Please double-check your diff and try > committing again. There is no bug

Re: SVN BUG : Lines disappeared after update and check in

2010-12-21 Thread Johan Corveleyn
the merge during >> the update didn't remove lines? >> >> BOb >> >> >> From: riad benmouhoub [mailto:riad.benmouh...@gmail.com] >> Sent: Tuesday, December 21, 2010 1:41 PM >> To: Bob Archer >> Subject: Re: SVN BUG : Lines disappeared after update

Re: SVN BUG : Lines disappeared after update and check in

2010-12-21 Thread riad benmouhoub
too.) > > > > BOb > > > > > > *From:* riad benmouhoub [mailto:riad.benmouh...@gmail.com] > *Sent:* Tuesday, December 21, 2010 1:41 PM > *To:* Bob Archer > *Subject:* Re: SVN BUG : Lines disappeared after update and check in > > > > Hi Bob, > >

RE: SVN BUG : Lines disappeared after update and check in

2010-12-21 Thread Bob Archer
> I experienced the following behavior with SVN. The steps i did are > : > > 1- I made changes in a file > 2- updated the file > 3- Checked in the file after the merge succeeded > 4- In the resulting file 6 lines disappeared. > > Is it considered as a bug? > has anyone experienced such a behavior

Re: SVN Bug? mergeinfo being stamped on wrong files

2010-03-06 Thread Stefan Sperling
On Fri, Mar 05, 2010 at 01:40:24PM -0500, Brad Heide wrote: > For example, when I look at the history of revision 31673 in branch > /modules/Core3/branches/3.12.x this is the only change in the log: > > /modules/Core3/branches/3.12.x/Res/Std/En_US/str/Global.string > > So revision 31673 had noth

Re: SVN Bug? mergeinfo being stamped on wrong files

2010-03-05 Thread Brad Heide
cc users@subversion.apache.org Subject Re: SVN Bug? mergeinfo being stamped on wrong files On Thu, Mar 04, 2010 at 04:27:16PM -0500, Brad Heide wrote: > C:\Dev\ModuleTests\Core3-3.15.x\Modules\Core>svn merge -c 38300 > ..\..\..\_Core3-trunk\Modules\Core > > (It just so happen

Re: SVN Bug? mergeinfo being stamped on wrong files

2010-03-05 Thread Stein Somers
One way to get mergeinfo on non-mergeinfo nodes is when you copy a directory. E.g. the repository has /trunk/dirA, without mergeinfo anywhere below /trunk. In a working copy on /trunk do: svn copy ^/trunk/dirA dirB Now dirB has mergeinfo that is not helping in any way. If you do ins

Re: SVN Bug? mergeinfo being stamped on wrong files

2010-03-05 Thread Stefan Sperling
On Thu, Mar 04, 2010 at 04:27:16PM -0500, Brad Heide wrote: > C:\Dev\ModuleTests\Core3-3.15.x\Modules\Core>svn merge -c 38300 > ..\..\..\_Core3-trunk\Modules\Core > > (It just so happens that revision 38300 has already been merged to this > branch so we expect the result of this merge operation