[Top][All Lists]

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

Re: [Axiom-developer] commit policy

From: Martin Rubey
Subject: Re: [Axiom-developer] commit policy
Date: Thu, 2 Dec 2004 17:28:07 +0100

I would suggest that you write a simple bug report and a simple patch and send
both to savannah. The patch should contain the bug number. After submitting the
patch you get a patch number. Then you comment the bug with the patch number.

This way
* it is clear that there was a bug
* it is clear that it is fixed.
* if the patch causes problems, it is easy to detect this and unapply it. (each
  release should contain notes which patches have been applied)

I'm ready to be convinced otherwise,


Stephen Wilson writes:
 > Tim, *
 > I have a simple patch which I am ready to upload. It fixes the
 > following bug:
 > ===============================================
 > (1) -> )f i n
 > BOOT>(quit)
 > -- restart Axiom
 > (1) -> )f
 >    Your command is ambiguous. The following are abbreviated by f :
 >       fin 
 >       frame 
 > (1) ->
 > ===============================================
 > The problem is in src/interp/int-top.boot, function `intloopPrefix?'.
 > Would you prefer I upload such changes to the axiom--language--1
 > branch, and send you notification that it would be relevant to
 > axiom--main--1? Or would you prefer a patch file and I'll simply keep
 > in sync with axiom--main--1? I have one more patch in the works
 > relevant to the main archive (a simple grammar issue in the message
 > database). 
 > Once the patch is applied, I would very much appreciate anyones
 > criticisms/comments regarding its style, etc. Its rather verbose for
 > such a small fix, but I thought it would be a perfect opportunity to
 > receive some feedback before I commit changes which involve more
 > involved issues. Please be harsh.
 > Thanks,
 > Steve
 > _______________________________________________
 > Axiom-developer mailing list
 > address@hidden

reply via email to

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