Redirecting Subversion to Git

135 views
Skip to first unread message

Thomas Broyer

unread,
Jun 22, 2014, 8:53:42 PM6/22/14
to google-web-tool...@googlegroups.com, Daniel Kurka
Hi all,

When we moved from SVN at code.google.com to Git at gwt.googlesource.com, I wanted to keep the SVN repo alive because there are many links to source files from blogs or sites like StackOverflow (I'm responsible for many of them).

In the last few days however, I've seen many people linking to code in the SVN repo's trunk rather than the Git repo's master.

I think this partly comes from the fact that the SVN repo is still linked to from https://code.google.com/p/google-web-toolkit/To browse the GWT source code, visit the 'Source' tab.
I've asked several time that this link be fixed but it's still not been done. It should link to https://code.google.com/p/google-web-toolkit/wiki/Source?tm=4 instead (what the Sources tab actually links to)

I'd also like to replace all files in the SVN trunk (not tags or release branches, only trunk) with dummy content pointing to gwt.googlesource.com. Something like:

Source code for the GWT project has moved to https://gwt.googlesource.com

The file you're looking for can be now found at https://gwt.googlesource.com/gwt/+/master/path/fo/file.java if it's not been deleted or renamed since then.

Specifically, I don't want to just delete the "trunk" branch from the SVN as that would break too many links. The "redirect" somehow "breaks" navigation (and particularly linking to a specific line in the file), but at least it's better than a plain 404.

What do you think?

Note: because I don't have commit rights to the SVN (maybe we could open that now that we no longer sync' from the Google repo?), I'll do a script that replaces the content for all the files in trunk, along with setting the mime type to text/plain, for someone else to run. Either that, or someone gives me the commit rights, after reviewing the script.

Daniel Kurka

unread,
Jun 22, 2014, 10:39:42 PM6/22/14
to google-web-tool...@googlegroups.com
I think updating the trunk branch is a good idea. I just gave you commit rights and I did hide the source tab from the project.


--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/19914684-71fb-49e5-b369-16157c68ac01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Google Germany GmbH
Dienerstr. 12
80331 München

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

Thomas Broyer

unread,
Jun 23, 2014, 3:57:11 AM6/23/14
to google-web-tool...@googlegroups.com
Thanks.

I'll post the script here for "review" before committing.
(I could also post the patch, I'm not sure it'll be that useful; maybe on gwt-code-reviews.appspot.com?)


On Monday, June 23, 2014 4:39:42 AM UTC+2, Daniel Kurka wrote:
I think updating the trunk branch is a good idea. I just gave you commit rights and I did hide the source tab from the project.
On Sun, Jun 22, 2014 at 5:53 PM, Thomas Broyer wrote:
Hi all,

When we moved from SVN at code.google.com to Git at gwt.googlesource.com, I wanted to keep the SVN repo alive because there are many links to source files from blogs or sites like StackOverflow (I'm responsible for many of them).

In the last few days however, I've seen many people linking to code in the SVN repo's trunk rather than the Git repo's master.

I think this partly comes from the fact that the SVN repo is still linked to from https://code.google.com/p/google-web-toolkit/To browse the GWT source code, visit the 'Source' tab.
I've asked several time that this link be fixed but it's still not been done. It should link to https://code.google.com/p/google-web-toolkit/wiki/Source?tm=4 instead (what the Sources tab actually links to)

I'd also like to replace all files in the SVN trunk (not tags or release branches, only trunk) with dummy content pointing to gwt.googlesource.com. Something like:

Source code for the GWT project has moved to https://gwt.googlesource.com

The file you're looking for can be now found at https://gwt.googlesource.com/gwt/+/master/path/fo/file.java if it's not been deleted or renamed since then.

Specifically, I don't want to just delete the "trunk" branch from the SVN as that would break too many links. The "redirect" somehow "breaks" navigation (and particularly linking to a specific line in the file), but at least it's better than a plain 404.

What do you think?

Note: because I don't have commit rights to the SVN (maybe we could open that now that we no longer sync' from the Google repo?), I'll do a script that replaces the content for all the files in trunk, along with setting the mime type to text/plain, for someone else to run. Either that, or someone gives me the commit rights, after reviewing the script.

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscribe@googlegroups.com.

Thomas Broyer

unread,
Jun 23, 2014, 11:08:31 AM6/23/14
to google-web-tool...@googlegroups.com
So, attached is the script I'm using (just after a clean "svn checkout").

I'll commit with message: "Replace all files with dummy content pointing to gwt.googlesource.com"
redirect.sh

Daniel Kurka

unread,
Jun 23, 2014, 11:12:40 AM6/23/14
to google-web-tool...@googlegroups.com
I think you attached the wrong script?!


To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/711b963f-07d7-4a9a-8e5e-05a0b5de86ce%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Thomas Broyer

unread,
Jun 23, 2014, 11:23:22 AM6/23/14
to google-web-tool...@googlegroups.com
Hahaha, made the mistake to copy the script in the SVN working copy so it was processed by itself!

Here is the script!
(hopefully)
redirect.sh

Thomas Broyer

unread,
Jun 25, 2014, 4:35:52 AM6/25/14
to google-web-tool...@googlegroups.com
As I didn't receive a NO-GO for it, I committed the result to SVN. It took hours (literally) but it's there: http://code.google.com/p/google-web-toolkit/source/detail?r=11669
(side note: I'm so glad we moved to Git!)

Patrick M. Tucker

unread,
Jun 27, 2014, 12:36:03 PM6/27/14
to google-web-tool...@googlegroups.com, dank...@google.com
There are still links on the gwtproject.org site that point to the old code.  For example: 

Daniel Kurka

unread,
Jun 27, 2014, 12:56:06 PM6/27/14
to Patrick M. Tucker, google-web-tool...@googlegroups.com
Hi Patrick,

do you mind sending a patch for gwt-site?

(Let me know if you need any help..)

-Daniel

Patrick Tucker

unread,
Jun 27, 2014, 1:11:24 PM6/27/14
to google-web-tool...@googlegroups.com
Unfortunately the chances that I get it done in a timely manner is very slim.

When I get some time I'm going to try setting up a windows port of curl and see if that will make it so I can easily commit patches at home.

Thomas Broyer

unread,
Jun 27, 2014, 3:08:26 PM6/27/14
to google-web-tool...@googlegroups.com, dank...@google.com
Reply all
Reply to author
Forward
0 new messages