Luke,
Definitely, i'm familiar with svn and will have no problem doing the import and
such. Let me know when the account is all situated and i'll get started. For
now, I have to head off to work :-)
Joseph Armbruster
Luke Dunstan wrote
/ others feel about having a layout like this:
/external
.. third party libs go here ..
/pythonce
/branches
/release24-maint
/release25-maint
/tags
/trunk (2.6 merge will go here)
It parallels the python svn repository on purpose.
Your thoughts?
Joseph Armbruster
Luke
if this was only done at
a rate of once per week.
Joseph Armbruster
On Tue, Mar 18, 2008 at 8:47 AM, Brad Clements [EMAIL PROTECTED] wrote:
Joseph Armbruster wrote:
Luke,
Cool, I was able to see it this morning. Quite empty indeed :-) I can
go
ahead and do the initial imports (if everyones ok
to treat
2.4 / 2.5. If they are strictly for maintenance (as svn.python.org) then
all we have to do is start out by placing them in their own branch and then
tag releases appropriately. From 2.6 on out, we could develop in trunk and
branch when necessary.
Joseph Armbruster
On Tue, Mar 18, 2008 at 9
All,
I will be in and out of #pythonce on freenode from here on out this evening.
Feel free to join me if you'd like to discuss merging and such.
Joseph Armbruster
___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo
does not trap the error, so it took a bit of tracing. This issue has
also been discussed on python-dev recently... I was able to successfully
complete a build with my tree merged over and should have my first commit in
tonight.
Cheers!
Joseph Armbruster
