Re: [python-committers] We will be moving to GitHub (hopefully) in2016

2016-01-04 Thread Donald Stufft
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 wrote: > > > >> On Mon, 4 Jan 2016 at 13:14 Donald Stufft

Re: [python-committers] We will be moving to GitHub (hopefully) in2016

2016-01-04 Thread Barry Warsaw
On Jan 04, 2016, at 02:09 PM, Guido van Rossum wrote: >I currently often rely on a single Hg clone containing all branches. I do hope that a single repo will contain all the branches, though I wouldn't mind too much if we split Python 2 and 3 into separate repos. git worktree is a nice tool if

Re: [python-committers] We will be moving to GitHub (hopefully) in2016

2016-01-04 Thread Guido van Rossum
On Mon, Jan 4, 2016 at 1:50 PM, Donald Stufft wrote: > 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. > Is the expectation that a Git clone would be significantly larger than an Hg clone of an

Re: [python-committers] We will be moving to GitHub (hopefully) in2016

2016-01-04 Thread Serhiy Storchaka
понеділок, 04-січ-2016 21:18:39 Brett Cannon написано: > On Mon, 4 Jan 2016 at 13:14 Donald Stufft wrote: > > On Jan 4, 2016, at 4:11 PM, Brett Cannon wrote: > > It’s pretty easy to migrate the entire history (at least what’s in Hg) > > including all branches