Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-11-02 Thread KHMan
grischka wrote: > From: "KHMan": > [snip snip] >> As for changesets, my plan is to name them using the revision >> numbers, like "cvs395.diff". I will keep a set of hg exports, like >> "hg395.diff". This is to preserve commit order. > > Hm, I don't understand exactly. Why do we need two sets of f

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-11-02 Thread Dave Dodge
On Fri, Nov 02, 2007 at 09:31:23AM -0600, Gregg Reynolds wrote: > On 11/2/07, KHMan <[EMAIL PROTECTED]> wrote: > > grischka wrote: > > > Do you think it is possible and/or makes sense to extract all > > > changesets from Rob's repo into single patches first, with an > > > automatic script or someth

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-11-02 Thread Gregg Reynolds
On 11/2/07, KHMan <[EMAIL PROTECTED]> wrote: > grischka wrote: > > Do you think it is possible and/or makes sense to extract all > > changesets from Rob's repo into single patches first, with an > > automatic script or something? In case you're not aware of it, check out Mercurial Queues (http://h

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-11-02 Thread grischka
From: "KHMan": > However I think some of David Dodge's patches have already been > applied, and bits of documentation has been updated in CVS, so I > guess that some hg patches will not apply cleanly. Yes, might happen, but we can deal with technical questions later. > I am doing this > on cygw

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-11-02 Thread KHMan
grischka wrote: > From: "KHMan": >> I will push patches to grischka, and check every few patches with >> Ubuntu "make all", and the two trees should come together. > > Do you think it is possible and/or makes sense to extract all > changesets from Rob's repo into single patches first, with an >

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-11-02 Thread grischka
From: "KHMan": > I will push patches to grischka, and check every few patches with > Ubuntu "make all", and the two trees should come together. Do you think it is possible and/or makes sense to extract all changesets from Rob's repo into single patches first, with an automatic script or somethi

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-10-30 Thread KHMan
grischka wrote: > From: "KHMan" >> Attached is a sample patch based on the Mercurial repository. > > Thanks Mr. KHMan. > I have committed this patch together with a Changelog entry to > the TinyCC CVS at Savannah. Oh, okay, I just checked the Savannah page and I won't bother David Wheeler an

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-10-30 Thread grischka
From: "KHMan" > Attached is a sample patch based on the Mercurial repository. Thanks Mr. KHMan. I have committed this patch together with a Changelog entry to the TinyCC CVS at Savannah. Please go on :) --- grischka ___ Tinycc-devel mailing lis

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-10-29 Thread KHMan
Dave Dodge wrote: > On Mon, Oct 29, 2007 at 02:59:15AM +0800, KHMan wrote: >> Attached is a sample patch based on the Mercurial repository. I >> assume revisions up to 395 is already in the official CVS, > > Just a quick note about mercurial: revision numbers such as 395 are > just a convenience a

Re: [Tinycc-devel] Sample patch from Mercurial repository

2007-10-29 Thread Dave Dodge
On Mon, Oct 29, 2007 at 02:59:15AM +0800, KHMan wrote: > Attached is a sample patch based on the Mercurial repository. I > assume revisions up to 395 is already in the official CVS, Just a quick note about mercurial: revision numbers such as 395 are just a convenience and are locally assigned to e

[Tinycc-devel] Sample patch from Mercurial repository

2007-10-28 Thread KHMan
Hi all, Attached is a sample patch based on the Mercurial repository. I assume revisions up to 395 is already in the official CVS, so perhaps I shall try and see how many trivial patches I can make from revision 396 onwards, versus current Savannah CVS. No quality assurance beyond trying a "make a