[EMAIL PROTECTED] writes:
| re: Stephen's patch
|
| A moment's thought will convince you that Stephen's patch is NOT
| a rework of an existing patch since the Makefiles are nowhere the same.
| Thus, since the idea was not previously posted as a diff-Naur to Gold
| it is NOT rework or cherry-picki
[EMAIL PROTECTED] writes:
[...]
| Those changes that I understood I picked up and merged into
| the new "silver" branch.
One aspect of a VCS such as SVN or GIT is that when someone
picks a change, it will pick it from a version number that controls
the whole branch. In a community effort, it
[EMAIL PROTECTED] writes:
> Future updates to "silver" will be complete changesets.
> The philosophy will be to try to "box up" a change so that it
> can be added or removed as a whole, which as far as I can tell
> is the whole reason for changesets.
I am curious about this point.
Does the patch
re: Stephen's patch
A moment's thought will convince you that Stephen's patch is NOT
a rework of an existing patch since the Makefiles are nowhere the same.
Thus, since the idea was not previously posted as a diff-Naur to Gold
it is NOT rework or cherry-picking.
Tim
_
Ah, controvery. Sigh.
I did a diff -r --brief axiom-gold-50 build-improvements and
the same with wh-sandbox. For each file that differed I tried
to (a) decide why the change was made, (b) how it was related
to other changes in the branch, (c) how it was related to the
original gold version, and (d
