On Fri, Jan 25, 2013 at 9:23 PM, Brandon Casey draf...@gmail.com wrote:
On Wed, Jan 23, 2013 at 12:36 PM, Junio C Hamano gits...@pobox.com wrote:
Sverre Rabbelier srabbel...@gmail.com writes:
On Wed, Jan 23, 2013 at 11:47 AM, John Keeping j...@keeping.me.uk wrote:
When did we last revisit
On Wed, Jan 23, 2013 at 12:36 PM, Junio C Hamano gits...@pobox.com wrote:
Sverre Rabbelier srabbel...@gmail.com writes:
On Wed, Jan 23, 2013 at 11:47 AM, John Keeping j...@keeping.me.uk wrote:
When did we last revisit what minimal python version we are ok with
requiring?
I was wondering if
On Sun, Jan 20, 2013 at 5:15 AM, John Keeping j...@keeping.me.uk wrote:
Although 2to3 will fix most issues in Python 2 code to make it run under
Python 3, it does not handle the new strict separation between byte
strings and unicode strings. There is one instance in
git_remote_helpers where
On Wed, Jan 23, 2013 at 11:20:39AM -0800, Sverre Rabbelier wrote:
On Sun, Jan 20, 2013 at 5:15 AM, John Keeping j...@keeping.me.uk wrote:
Although 2to3 will fix most issues in Python 2 code to make it run under
Python 3, it does not handle the new strict separation between byte
strings and
Sverre Rabbelier srabbel...@gmail.com writes:
On Wed, Jan 23, 2013 at 11:47 AM, John Keeping j...@keeping.me.uk wrote:
When did we last revisit what minimal python version we are ok with
requiring?
I was wondering if people would weigh in discussing that in response to
[1] but no one has
Although 2to3 will fix most issues in Python 2 code to make it run under
Python 3, it does not handle the new strict separation between byte
strings and unicode strings. There is one instance in
git_remote_helpers where we are caught by this, which is when reading
refs from git for-each-ref.
Fix
6 matches
Mail list logo
