Felipe Contreras felipe.contre...@gmail.com writes:
The previous version had an indentation bug (did I mention I hate python?).
A few fixes to be applied on top of the massive changes already queued.
Nothing
major.
[2/2] may not matter much in the context of my tree (people would
use post
On Sun, May 5, 2013 at 1:33 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
The previous version had an indentation bug (did I mention I hate python?).
A few fixes to be applied on top of the massive changes already queued.
Nothing
major.
On Sun, May 5, 2013 at 2:03 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
On Sun, May 5, 2013 at 1:33 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
The previous version had an indentation bug
On Sun, May 5, 2013 at 3:58 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
So do you want to queue these on top of the massive in 'next', not
directly on 'master'?
If they apply on master, master. But I'm confused, are the massive
changes not
Hi,
The previous version had an indentation bug (did I mention I hate python?).
A few fixes to be applied on top of the massive changes already queued. Nothing
major.
Felipe Contreras (2):
remote-bzr: convert all unicode keys to str
remote-bzr: avoid bad refs
5 matches
Mail list logo