Hi all
I think that a good practice to ancourage and ease the review of
updates is splitting a pull request in at least two commits: one for
the initial convert-ly and the second for the manual changes.
I think it may be added to the wiki page:
Federico Bruni f...@inventati.org writes:
Hi all
I think that a good practice to ancourage and ease the review of
updates is splitting a pull request in at least two commits: one for
the initial convert-ly and the second for the manual changes.
I think it may be added to the wiki page:
2014-02-22 16:46 GMT+01:00 Federico Bruni f...@inventati.org:
I have a question: do you know why git diff after convert-ly doesn't show a
proper diff line by line? I've already read a complain about this from Keith
on lilypond-user, pointing to this commit:
$ file -i ftp/ScriabinA/O59/prelude/prelude.ly
ftp/ScriabinA/O59/prelude/prelude.ly: text/plain; charset=us-ascii
Can I run iconv on it, right?
This again will break the diff (see previous thread), but it's needed.
One more thing to add to the wiki? If you give me the ok, I can edit
the page
Il sab, feb 22, 2014 at 6:38 , Federico Bruni f...@inventati.org ha
scritto:
$ file -i ftp/ScriabinA/O59/prelude/prelude.ly
ftp/ScriabinA/O59/prelude/prelude.ly: text/plain; charset=us-ascii
Can I run iconv on it, right?
This again will break the diff (see previous thread), but it's
needed.
Federico Bruni f...@inventati.org writes:
Il sab, feb 22, 2014 at 6:38 , Federico Bruni
f...@inventati.org ha scritto:
$ file -i ftp/ScriabinA/O59/prelude/prelude.ly
ftp/ScriabinA/O59/prelude/prelude.ly: text/plain; charset=us-ascii
Can I run iconv on it, right?
This again will break the
Il sab, feb 22, 2014 at 7:12 , Noeck noeck.marb...@gmx.de ha scritto:
Hi,
I might be wrong, but the file has no property like utf8 orascii,
it
is just encoded as such. Ascii is a subset of utf8. If there are only
ascii charachters in the file, there is no reason for the file command
to say
