[Bug web/90334] documentation for getting read-write SVN access is misleading

2019-07-05 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #8 from Jonathan Wakely  ---
Fixed by https://gcc.gnu.org/ml/gcc-patches/2019-07/msg00435.html - thanks

[Bug web/90334] documentation for getting read-write SVN access is misleading

2019-07-05 Thread author at shakthimaan dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334

--- Comment #7 from Shakthi Kannan  ---
Created attachment 46559
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46559=edit
Use whitespace between sourceware.org and gcc.gnu.org

[Bug web/90334] documentation for getting read-write SVN access is misleading

2019-07-01 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334

Eric Gallager  changed:

   What|Removed |Added

 CC||egallager at gcc dot gnu.org

--- Comment #6 from Eric Gallager  ---
(In reply to Jonathan Wakely from comment #5)
> Maybe just saying "sourceware.org / gcc.gnu.org" would be good enough to
> avoid confusion. That's obviously not a URL that you're supposed to copy &
> paste.

Yes, that would be an improvement.

[Bug web/90334] documentation for getting read-write SVN access is misleading

2019-07-01 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334

--- Comment #5 from Jonathan Wakely  ---
Maybe just saying "sourceware.org / gcc.gnu.org" would be good enough to avoid
confusion. That's obviously not a URL that you're supposed to copy & paste.

[Bug web/90334] documentation for getting read-write SVN access is misleading

2019-07-01 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334

--- Comment #4 from Andrew Pinski  ---
So two things:
1) sourceware.org/gcc.gnu.org is a standard way of saying the machines are the
exact same machine.  This is NOT an URL.  It is like writing "glass/mug you
have is nice looking".  

https://www.grammarly.com/blog/slash/

2) The no link for the email address is to reduce the spam to that email
address.

[Bug web/90334] documentation for getting read-write SVN access is misleading

2019-07-01 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334

--- Comment #3 from Jonathan Wakely  ---
Or in other words...

(In reply to Roland Illig from comment #0)
> Therefore I pasted sourceware.org/gcc.gnu.org to the URL bar of my browser
> and got redirected to https://sourceware.org/gcc.gnu.org, which says 404.

So don't do that then :-)

[Bug web/90334] documentation for getting read-write SVN access is misleading

2019-07-01 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334

--- Comment #2 from Jonathan Wakely  ---
But "or" would be wrong because there is only one server and only one account.
You can't have an account on sourceware.org and not on gcc.gnu.org, or vice
versa.

And you certainly can't have an account on http://sourceware.org/gcc.gnu.org
because you have an account on the server, not some URL. What were you
expecting that "link" to go to? Your account?

It might be better to use mailto: for the email address, but I'm not convinced
your suggestion would be an improvement.

[Bug web/90334] documentation for getting read-write SVN access is misleading

2019-06-30 Thread author at shakthimaan dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334

Shakthi Kannan  changed:

   What|Removed |Added

 CC||author at shakthimaan dot com

--- Comment #1 from Shakthi Kannan  ---
Confirmed.