Sounds like you aren't exactly a DVCS fan...


On Tue, Feb 18, 2014 at 8:46 PM, Guido van Rossum <guido@python.org> wrote:
I do think there's one legitimate concern -- someone might pull a diff from Larry's branch and then accidentally push it back to the public repo, and then Larry would be in trouble if he was planning to rebase that diff. (The joys of DVCS -- we never had this problem in the cvs or svn days...)

Publishing tarballs would prevent this and still let people test the exact code Larry is assembling on their favorite obscure platform.


On Tue, Feb 18, 2014 at 3:54 PM, Barry Warsaw <barry@python.org> wrote:
On Feb 19, 2014, at 12:38 AM, Matthias Klose wrote:

>Am 17.02.2014 00:25, schrieb Larry Hastings:
>> And my local branch will remain private until 3.4.0 final ships!
>
>sorry, but this is so wrong. Is there *any* reason why to keep this branch
>private?

IMO, no.  read-only for !larry sure, but not private.

-Barry



--
--Guido van Rossum (python.org/~guido)

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com




--
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple: "It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was nul-terminated."