Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| > It is good to have unstable branch where experiments are
| > conducted.
|
| Yes, I think that is good. You will probably suggest that for those
| experimental branches there might be other people responsible not you.
|
| GNU ARCH lets you do
Hi Gaby,
I agree. Well, almost. Almost because I do not believe *every* patch
should be applied to the branch.
You probably have more years of experience than me. ;-)
I believe patches that survive public review should be
> immediately applied.
Fine.
It is good to have unstable branch w
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| Hi Gaby,
|
| I am happy that you raised that problem.
|
| On 04/05/2006 06:30 AM, Gabriel Dos Reis wrote:
|
| > and expertise. Key factors for that, I believe, are:
| >* instant availability of patches applied to mainline
|
| Well, it should be
Hi Gaby,
I am happy that you raised that problem.
On 04/05/2006 06:30 AM, Gabriel Dos Reis wrote:
and expertise. Key factors for that, I believe, are:
* instant availability of patches applied to mainline
Well, it should be very simple that any patch that is sent to Tim is
immediately
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Tuesday, April 04, 2006 10:56 PM Gabriel Dos Reis wrote:
| > ...
| > Somehow I understood that the "wider" public will see only
| > the two-month interval, while the developers could see
| > immediate patches (I'm mostly initerested in the other
| > ch
On Tuesday, April 04, 2006 10:56 PM Gabriel Dos Reis wrote:
> ...
> Somehow I understood that the "wider" public will see only
> the two-month interval, while the developers could see
> immediate patches (I'm mostly initerested in the other
> changes that were suggested and applied, not in the "end
root <[EMAIL PROTECTED]> writes:
| it's still at patch-47.
| updates are done on a best-effort, two-month interval.
| i've been heavily buried in work, working hard on the
| maple integration-bug study, and dealing with an
| evolving personal issue which has caused a lag.
| i'm in the process o
it's still at patch-47.
updates are done on a best-effort, two-month interval.
i've been heavily buried in work, working hard on the
maple integration-bug study, and dealing with an
evolving personal issue which has caused a lag.
i'm in the process of creating a new patch now.
testing is going
root <[EMAIL PROTECTED]> writes:
| patch applied.
| fixed in the next release.
Thanks!
Is there a way to have the revision number (version number?) at which
the trunk is on a daily basis? I find that to be a very useful
functionality for tracking the various branches and revisions (and
checking
patch applied.
fixed in the next release.
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
10 matches
Mail list logo
