IMPORTANT: New hg repo coming!
0 views
Skip to first unread message
Bruce Frederiksen
Mar 9, 2010, 1:56:34 PM3/9/10
to AVR compiler google group
Hi Everybody,
Looks like we're going to Python3!
I would also like to clean up our repository while we're making these other changes. Thus, we'll combine moving from wx to http, Python2 to Python3, moving to a new version of doctest-tools with rebuilding our mercurial repository and get it all of the way in one big
What I'm thinking is to move the current repo off to the side (called either wx or Python2 or ??), rebuild our repo to take out the branches (oops!) and old image files, convert the project to Python3 and create a new "default" repo. I'll leave the gui stuff for reference while we convert over to the http version.
IMPORTANT, PLEASE READ!
What this means is that you will no longer be able to push changesets from the clones of the current repo up to the new repo. In other words, you are all going to have to delete all copies (including your "google" copy) of the current repo and start from scratch with the new repo, starting with your "google" copy.
So if anybody has made any changes that have not yet been pushed to google, PLEASE LET ME KNOW so that I don't blow you out of the water! I plan to do this later this week or this weekend and will send out another email when it's done.
Thanks!
-Bruce
Looks like we're going to Python3!
I would also like to clean up our repository while we're making these other changes. Thus, we'll combine moving from wx to http, Python2 to Python3, moving to a new version of doctest-tools with rebuilding our mercurial repository and get it all of the way in one big
What I'm thinking is to move the current repo off to the side (called either wx or Python2 or ??), rebuild our repo to take out the branches (oops!) and old image files, convert the project to Python3 and create a new "default" repo. I'll leave the gui stuff for reference while we convert over to the http version.
IMPORTANT, PLEASE READ!
What this means is that you will no longer be able to push changesets from the clones of the current repo up to the new repo. In other words, you are all going to have to delete all copies (including your "google" copy) of the current repo and start from scratch with the new repo, starting with your "google" copy.
So if anybody has made any changes that have not yet been pushed to google, PLEASE LET ME KNOW so that I don't blow you out of the water! I plan to do this later this week or this weekend and will send out another email when it's done.
Thanks!
-Bruce
Reply all
Reply to author
Forward
0 new messages