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
> 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
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 successful also .
3)Any other combinations is not working but the 2 combinations(1
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
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 client: An add and a following commit results in a htt
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
Hi svn developers,
once I tried to commit txt file with these two lines:
RUNNING:
===
written inside, I got following error message:
[tjavurek@lxplus0057]~/pMSSM/BooFactory/Tools2% svn ci -m
"" error.txt
Sendingerror.txt
Transmitting file data .svn: Commit failed (details
follow):
Am 14.10.2011 10:27, schrieb Romain Raveaux:
with as much information as possible about what
^^^
you were trying to do.
But please first search the mailing list archives for the error message
^^
There was a bu
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
(users@subversion.apache.org)
with as much information as possible about what
you were trying to do.
But please
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
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,
>
>
> 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
Hi,
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?
Thanks
Riad
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
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
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
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
Hi.
This is my first attempt at making a bug report to this group. Hopefully
I'll get it right.
SVN server version: 1.6.5. Build: Tigris.org, Apache 2.2 compatible,
maintained by D.J. Heap, Branko Čibej and Troy Simpson)
SVN client version: 1.6.9. Build: Collabnet, Windows version.
Client OS: W
Hello,
I'm hitting what appears to be a bug in subversion. The problem is that I get
incorrect subtree mergeinfo after a merge to my branch; the subtree is not
recording the merge, and this later prevents reintegrate from working (via
"Reintegrate can only be used if revisions [X] through [Y] w
19 matches
Mail list logo
