|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MGWT-334) Add support for SuperDev... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Olivier Lamy (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Olivier Lamy (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)

Aahhh, we wouldn't have this discussion if Nicolas had been clear about what the process is/should be (i.e. mirror changes on both repos).
...and there have been changes on svn.codehaus that have not been mirrored to GitHub either.
As far as process goes, I don't have any real issue with svn.codehaus (besides having to sync 2 repos). I'll try to sync the repos, unfortunately, we don't have Nicolas' authors file, so sync'ing from svn.codehaus to GitHub will be a bit harder, and hard to reproduce, because of mismatching; I think I'll simply make one big "sync" commit on each side.
(btw, GWT will soon switch to Git
and they currently actually use Perforce as everything within Google, and mirror to SVN)