[Top][All Lists]

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

Re: [Tinycc-devel] Newer tinycc repository?

From: KHMan
Subject: Re: [Tinycc-devel] Newer tinycc repository?
Date: Tue, 30 Oct 2007 11:34:11 +0800
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070802 SeaMonkey/1.1.4

Simon 'corecode' Schubert wrote:
> KHMan wrote:
>> Looks like some pretty extensive changes, including directory
>> structure changes and refactoring. The question now is: Should all
>> of Rob's tree go into the official CVS?
> [snip] Declare one repo as "common denominator".

Nobody's offering any yet, just Nick's SVN on 20070908 which
nobody really replied to. Any revision control is fine, if someone
would just take the lead, but obviously some people would perceive
little gain going from CVS to Nick's SVN.

So regardless of the revision control issue, well, someone still
needs to come up and declare himself as the "common denominator".

> [snip] tcc's official repo is undermaintained since time anyways.  I don't
> see any benefit in trying to funnel all patches into CVS, which is a
> time consuming process, if you can instead just leverage the distributed
> nature of mercurial.

If the official tcc is correctly sync'ed, updating CVS based on
exports from hg should be quite easy, I suppose. All we need is a
little planning.

I don't plan to bother everyone with this thorny CVS issue anymore
than necessary. This is just a bunch of largely unskilled clerical
donkey work that I can try to do. I'll try to contact David
Wheeler and see if he will accept the updates, then I'll report
back to the list. If I get stuck, then too bad, at least I've tried.

In the meantime, I'm not standing in the way of anything -- my
foolish attempt to update the CVS has no bearing on the actions of
our heroes wielding Mercurial -- so for the third time, I'd say
that we now need someone to take some kind of lead...

Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia

reply via email to

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