Hello Michael,
On Sun, Oct 16, 2016 at 5:59 PM, Michael Matz wrote:
>
> You can't "move" tinycc anyway.
>
Of course not. There are only a handful of folks who really understand the
inner workings of tcc (you being one of them), and if they want to stick
with repo.or.cz, then that's where code
Hi,
On Sun, 16 Oct 2016, avih wrote:
Overall, I'd vote to move tinycc to github, with the caveat that it'd be
nice to also have an external archive of all the discussions, issues,
reviews, etc.
You can't "move" tinycc anyway. If people want to start using github:
more power to them, repo.o
avih, one more note:
The big problem is not how we handle our discussions on the mailing list,
it's when a person does not respect the open source governance and pushes a
bunch of unsolicited commits without *any* discussion. This has happened
many times over the last three or four years. Pull req
Hey everyone,
I owe an apology to grishka. Grishka, I may not like how you currently
handle unwanted pushes (often by revert without discussion), but I don't
think you'd be half as reactive if we kept unwanted pushes out of the main
repo in the first place. In that case we'd get the best of your e
On Sun, Oct 16, 2016 at 11:26 AM, avih wrote:
> > I am less concerned about losing this kind of meta-info, as I expect we
> would continue discussion primarily on the mailing list.
>
> Would you/we?
>
> The initial suggestion mentioned pull-requests as being easier to handle
> than discussing pat
to a ticket
$ git commit –m “Fix std library path with –run on FreeBSD, refs #6”
This is something redmine (http://www.redmine.org/) can do for example.
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On
Behalf Of David Mertens
Sent: dimanche 16
I am less concerned about losing this kind of meta-info, as I expect we
would continue discussion primarily on the mailing list. Mailing lists seem
to me to be much better venues for discussion than the facilities provided
by github.
My bigger concern is: who would be the project managers? Who wou
Hi,
on Github we could use Travis to run tests after every commit.
We could also use Qemu there to check if the other architectures still
work. It might also serve as an example how to setup a cross development
environment with TinyCC.
Best regards.
Daniel
I would like to have the ability to contribute to
tcc in a more structured fashion. I have been working
to get tcc to build/run on cygwin but only in private work.
Without a way to publicly contribute to tcc development
I have little hope of having other contributers to assist
with the cygwin wo
...@nongnu.org] On
Behalf Of David Mertens
Sent: samedi 15 octobre 2016 18:58
To: tinycc-devel@nongnu.org
Subject: [Tinycc-devel] Governance (Re: cleanups)
Hello all,
Jean-Claude articulates concerns I have felt as well. Sometimes we'll get a
series of ridiculous commits from hitherto un
Hello all,
Jean-Claude articulates concerns I have felt as well. Sometimes we'll get a
series of ridiculous commits from hitherto unknown programmers trying to
"help". Sometimes we get commits from people trying to extend tcc's
behavior beyond its core intent. Other times core hackers (OK, mostly
11 matches
Mail list logo
