[python-committers] We will be moving to GitHub (hopefully) in2016
donald at stufft.io
Mon Jan 4 16:50:13 EST 2016
I'm not sure that you'd see much savings. You'd only get deltas that were never merged to master excluded. Point taken though.
Sent from my iPhone
> On Jan 4, 2016, at 4:18 PM, Brett Cannon <brett at python.org> wrote:
>> On Mon, 4 Jan 2016 at 13:14 Donald Stufft <donald at stufft.io> wrote:
>>> On Jan 4, 2016, at 4:11 PM, Brett Cannon <brett at python.org> wrote:
>>> On Mon, 4 Jan 2016 at 13:08 Steve Dower <steve.dower at python.org> wrote:
>>>> I've found that hggit works very well - I used it to migrate my work project to github and still use it to avoid having to deal with git. (My intent is to keep using it for Python as well.)
>>>> Is the plan to migrate the entire history or just master?
>>> TBD. Email beginning to outline the dependency graph for the transition forthcoming once I finish a code review at work that some co-worker handed to me when he went off to Australia for an extended holiday. ;)
>> It’s pretty easy to migrate the entire history (at least what’s in Hg) including all branches and tags.
> It's not about the difficulty as the size of the clone. E.g., if we make Python 2 a separate repo does it buy us a lot of space savings (we need to remember not everyone has broadband, so there is some potential balance to be had between history vs. clone size)?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the python-committers