[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Roadmap for 0.9.26?

From: grischka
Subject: Re: [Tinycc-devel] Roadmap for 0.9.26?
Date: Wed, 18 May 2011 00:39:29 +0200
User-agent: Thunderbird (Windows/20100228)

Thomas Preud'homme wrote:
I updated the Changelog a bit, see last commit.

I would certainly remove the entry about support for indirect functions as external if needed. It's a very small patch which doesn't deserve credit. I put it here in the first place only because lots of questions were asked on the ML about this.

What's an "indirect function", anyway?

I'd suggest to remove everything that users can't understand.
(e.g. tcc_open_bf, __TRY__, "Split libtcc1.a build", ...)

However I think we should keep reverse order in time, that is last
added features at top.

Anyway, I do not plan to review commits again this time so we will just
go with current "mob" state as is, unless otherwise suggested.
Maybe for next branch we could help you by using some home-made tagging, like Fix: commit_sha1 lines. This way you know which commit to merge (and you would take the commit message of the first commit in a chain). I should be relatively easy to write a script to automate that.

Automate what?  I'll just reset master to current mob, in fact I just
did it.  We can still add more commits of course.   Of course it is
also still possible to remove commits and to rebuild the entire branch
since last release, but I don't plan to do some such myself.

Btw, as to your last commit with Makefiles

   +export LIBTCC1
I don't think using export makes sense since the top-level Makefile is
already included (at tests/Makefile:15).

    +ifdef LIBTCC1
LIBTCC1 may be empty but defined, as from Makefile:142:

--- grischka

reply via email to

[Prev in Thread] Current Thread [Next in Thread]