[EMAIL PROTECTED] (Jack Howarth) writes:
> Has anyone else had problems accessing the svn server today
> for gcc? I tried from home and work today. In both cases, the
> 'svn update' never produces any updates of new files or completes.
This should now be fixed.
We were being hit hard by a si
Yes, I noticed that and sent a mail to [EMAIL PROTECTED]
You can workaround by relocating the working copy to use http:// instead, as in:
svn switch --relocate svn://gcc.gnu.org/svn/gcc/trunk
http://gcc.gnu.org/svn/gcc/trunk
On 13/09/06, Jack Howarth <[EMAIL PROTECTED]> wrote:
Has anyone
Jack Howarth wrote:
Has anyone else had problems accessing the svn server today
for gcc? I tried from home and work today. In both cases, the
'svn update' never produces any updates of new files or completes.
Jack
I was beginning to think I was the only one.
I did a s
Has anyone else had problems accessing the svn server today
for gcc? I tried from home and work today. In both cases, the
'svn update' never produces any updates of new files or completes.
Jack
Andrew Pinski <[EMAIL PROTECTED]> writes:
> On May 2, 2006, at 6:34 PM, Mike Stump wrote:
>>
>>> Also, with svn 1.4 dev (all i have on this machine)
>>
>> Cool, fixed in 1.4 dev. Now I'm curious if it is fixed in 1.3.x. I
>> really want to update, but, the fortunes of a large company with lots
Mike Stump <[EMAIL PROTECTED]> wrote:
>> Also, with svn 1.4 dev (all i have on this machine)
>
> Cool, fixed in 1.4 dev. Now I'm curious if it is fixed in 1.3.x. I
> really want to update, but, the fortunes of a large company with lots
> of revenue are predicated on this stuff actually working.
On May 2, 2006, at 6:38 PM, Andrew Pinski wrote:
I even tried following your directions and it worked for me without
conflicts.
I had to replace 4:6 with 3:5 but other than that it worked.
And this was with 1.3.0.
Hum... :-( Thanks for the data point. Might just be me, with a
codegen bug
On May 2, 2006, at 6:34 PM, Mike Stump wrote:
Also, with svn 1.4 dev (all i have on this machine)
Cool, fixed in 1.4 dev. Now I'm curious if it is fixed in 1.3.x.
I really want to update, but, the fortunes of a large company with
lots of revenue are predicated on this stuff actually
On May 2, 2006, at 6:05 PM, Daniel Berlin wrote:
What happened to rev3?
I did a svn mkdir brnaches && svn mv brnaches branches, but didn't
want to fess up to it.
Also, with svn 1.4 dev (all i have on this machine)
Cool, fixed in 1.4 dev. Now I'm curious if it is fixed in 1.3.x. I
rea
> mrs $ svn ci .
> Adding trunk/file1
> Transmitting file data .
> Committed revision 2.
> mrs $ svn cp file:///Volumes/mrs4/svn-repo/trunk file:///Volumes/mrs4/
> svn-repo/branches/rel
> Committed revision 4.
What happened to rev3?
Also, with svn 1.4 dev (all i have on this machine), i
On May 1, 2006, at 9:17 PM, Diego Novillo wrote:
It amazes me that svn can't do a merge.
You obviously have not read the documentation nor browsed the GCC
wiki.
Doing merges with svn is amazingly simple.
I look forward to your answer I put to Ben.
On May 1, 2006, at 8:58 PM, Steven Bosscher wrote:
On 5/2/06, Mike Stump <[EMAIL PROTECTED]> wrote:
It amazes me that svn can't do a merge.
Just because you can't do it, doesn't mean svn can't do it.
Let me know if you can reproduce what I see with your version of
svn. Feel free to answer
On May 1, 2006, at 8:48 PM, Ben Elliston wrote:
It amazes me that svn can't do a merge.
That's patently inaccurate.
Ok, try this out:
mrs $ mkdir svn-repo
mrs $ svnadmin create svn-repo
mrs $ svn co file:///Volumes/mrs4/svn-repo svn
Checked out revision 0.
mrs $ cd svn
mrs $ svn mkdir trunk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Stump wrote:
> It amazes me that svn can't do a merge.
>
You obviously have not read the documentation nor browsed the GCC wiki.
Doing merges with svn is amazingly simple.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEV
On 5/2/06, Mike Stump <[EMAIL PROTECTED]> wrote:
It amazes me that svn can't do a merge.
Just because you can't do it, doesn't mean svn can't do it. Other
people have been maintaining branches with svn for months now without
trouble.
Gr.
Steven
> Well, conceptually, I want the history for the file, hence the cp. I
> was trying to get around yet another svn bug that causes checkins of
> merge products to fail.
What bugs?
If you file them, and tell us how to reproduce them, maybe we could fix
them?
> It amazes me that svn can't do a merge.
That's patently inaccurate.
Have you tried using the svnmerge script that uses SVN properties to
remember which changesets you have (and haven't) merged?
Ben
On May 1, 2006, at 7:43 PM, Paul Brook wrote:
What exactly are you trying to achieve?
The first order operation is is a new fangled concept called a
merge. The second order operation is to dig out from under svn bugs
with additional commands to get the state of the working copy
correct,
> mrs $ svn cp -r113703 svn+ssh://src.apple.com/svn/fsf-gcc/gcc/
> branches/apple-local-200502-branch/gcc/testsuite/g++.dg/
> bitreverse-10.C bitreverse-10.C
> svn: Entry for 'bitreverse-10.C' exists (though the working file is
> missing)
>
> How do I `fix' this. I know how to fix it with multiple
svn is giving me grief, I'm merging and getting:
mrs $ svn cp -r113703 svn+ssh://src.apple.com/svn/fsf-gcc/gcc/
branches/apple-local-200502-branch/gcc/testsuite/g++.dg/
bitreverse-10.C bitreverse-10.C
svn: Entry for 'bitreverse-10.C' exists (though the working file is
missing)
mrs $ svn add
20 matches
Mail list logo
