Re: GUB usage

[Jordi Gutiérrez Hermoso]

On 14 March 2013 05:14, Jan Nieuwenhuizen <address@hidden> wrote:
> Jordi Gutiérrez Hermoso writes:
>
>> Where are these two other branches?
>
> Follow github's forks
>
>     https://github.com/janneke/gub/network
>
> then look at branches.  Here
>
>     https://github.com/janneke/gub/branches

I prefer to avoid using non-free software for development. It's
important to not depend on github's features for GNU:

   http://mako.cc/writing/hill-free_tools.html

I already have your public branches in my hg clone:

    http://hg.octave.org/gub/bookmarks

> I have at least two unpublished branches with conflicting changes
> (patches for specific LilyPond releases and mingw cross building).

If you would like me to merge the whitespace changes into those
branches, please publish them.

> AFAIC Denemo is here
>
>     https://github.com/jjbenham/gub

Thanks, I'll see what I can merge from them.

> Just make sure that you avoid making whitespace changes manually and
> check-in the final whitespace cleanup script, eg as bin/2pep-8.py.

No, I have to do it somewhat manually. Good style is a matter of
taste, not automation. PEP-8 itself says that sometimes you should
break some elements of it when you deem it's more readable otherwise:

    
http://www.python.org/dev/peps/pep-0008/#a-foolish-consistency-is-the-hobgoblin-of-little-minds

I don't mind merging my changes and doing all the pepeighting
manually. But if we are going to do this, you have to be aware of
PEP-8 yourself and agree to mostly follow it from now on. The only
glaring problem I see is very long lines that should be broken up into
shorter lines. If you're using Emacs, its default X frame is already
80 columns wide.

- Jordi G. H.