> On 12 May 2016, at 23:48, Iavor Diatchki wrote:
>
>
> On Sat, May 7, 2016 at 1:44 AM, Jon Fairbairn
> wrote:
>
>
> The one this violates is “never make language design decisions
> to work around deficiencies in tools” The problem is that diff
> does its work in ignorance of the syntax and
Hello,
what is the status of the discussion about how we should collaborate? I
am not picky and would be happy to use whatever tools others prefer. If it
was left to me, I'd use: 1) a git repo on github, which contains the
current version of the report, and various proposals, and 2) this e-mail
Hello!
On 2016-05-31 at 19:50:54 +0200, Iavor Diatchki wrote:
> what is the status of the discussion about how we should collaborate?
> I am not picky and would be happy to use whatever tools others prefer.
> If it was left to me, I'd use: 1) a git repo on github, which contains
> the current ver
On 31/05/2016, Herbert Valerio Riedel wrote:
> I'd rather suggest to have 2 Git repos, to keep the concerns separate.
> And I think we can just start out with such a 2nd GitHub repo and
> make the process up as we go. At this point we should just get moving, as I
> sense many of you want to finall
On 2016-05-31 at 15:42:14 +0200, Antonio Nikishaev wrote:
[...]
> Personally I don't need this extension per se since I don't care about one
> excess diff line.
> What I do care about however, is the horrendous style people invented to
> avoid “the diff problem”.
> As an example
>
> something =
