On 2016-08-28 08:47 AM, Jiří Techet wrote:
Hi Matthew,
some random thoughts.
I'm not sure I agree with doing lots of changes on a separate branch
basically without any review. While you will be able to commit things fast
to the branch, the most probable outcome will be the branch will get
Hi Matthew,
some random thoughts.
I'm not sure I agree with doing lots of changes on a separate branch
basically without any review. While you will be able to commit things fast
to the branch, the most probable outcome will be the branch will get never
merged because either nobody will be able
On 2016-08-27 03:13 AM, Colomban Wendling wrote:
Le 27/08/2016 à 06:17, Lex Trotman a écrit :
[...]
Yes, and might be even simpler if it can take advantage of any of the
new plugin capabilities. IIRC filetypes are never unloaded after
loading, so the plugins would have to be the same.
On 2016-08-27 12:38 AM, Lex Trotman wrote:
[...]
My proposition is that people without time or knowledge not contribute to
the development of this enhancement. Of course everyone would be able to
comment on stuff as it is merged back into master, but only those willing to
actively develop the
[...]
> My proposition is that people without time or knowledge not contribute to
> the development of this enhancement. Of course everyone would be able to
> comment on stuff as it is merged back into master, but only those willing to
> actively develop the solutions have any kind of strong voice
On 2016-08-26 09:17 PM, Lex Trotman wrote:
[...]
I just meant for that meta tracker issue. It gets too hard to keep track of
what's going on when there's dozens and dozens of comments. I would expect
code-related discussions to happen on the individual PRs or separate ML
threads.
I was
[...]
> I just meant for that meta tracker issue. It gets too hard to keep track of
> what's going on when there's dozens and dozens of comments. I would expect
> code-related discussions to happen on the individual PRs or separate ML
> threads.
I was thinking of the design discussion (see below)
On 2016-08-26 01:34 PM, Thomas Martitz wrote:
Uhm, where did this thread start? Who are you replying to?
My bad, I should've also sent a mail to the list. I assumed most of the
main dev contributors got mail from Github about the Issue I posted, and
anyone else would jump in as interested.
On 2016-08-26 12:13 AM, Lex Trotman wrote:
Not sure I agree that Github is bad for *development* discussions, for
users, sure, the ML is likely to find the audience better, but most
developers will also be githubians. Also github supports markup that
mail doesn't. But anyway lets try mailing it
Uhm, where did this thread start? Who are you replying to?
Am 26.08.2016 um 09:13 schrieb Lex Trotman:
Not sure I agree that Github is bad for *development* discussions, for
users, sure, the ML is likely to find the audience better, but most
developers will also be githubians. Also github
10 matches
Mail list logo
