[Pharo-project] About fixes for noury and other
Hi noury I started to harvest your fixes and I learned something :) when most of your fixes are about extending or changing a package just publish a new version of that package. This way I can use the merge tool and be much more efficient, do not create a specific package with specific class extension for it else I have to modify everything by hand. Stef
Stéf, On 11 sept. 08, at 09:44, Stéphane Ducasse wrote:
Hi noury
I started to harvest your fixes and I learned something :) when most of your fixes are about extending or changing a package just publish a new version of that package. This way I can use the merge tool and be much more efficient, do not create a specific package with specific class extension for it else I have to modify everything by hand.
This sounds like a cleaner way indeed. If you didn't finish harvesting it, I can split different changes as you suggest. Noury ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------
Stéf, On 11 sept. 08, at 21:32, Noury Bouraqadi wrote:
On 11 sept. 08, at 09:44, Stéphane Ducasse wrote:
Hi noury
I started to harvest your fixes and I learned something :) when most of your fixes are about extending or changing a package just publish a new version of that package. This way I can use the merge tool and be much more efficient, do not create a specific package with specific class extension for it else I have to modify everything by hand.
This sounds like a cleaner way indeed. If you didn't finish harvesting it, I can split different changes as you suggest.
Did you harvested my previous fixes ? Cause I added an extra bug fix (attached) to the class builder to avoid the creation of "zombie" classes (classes not in the SystemDictionary => Memory leak) when class variable names are lowercase. The test BTW, where one can check to see if a package has been harvested? Noury ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------
Normally when you enter a bug fix in the issue I will close it when it is harvested/refused.... I will do the classbuilder related ones now. Stef On Sep 12, 2008, at 7:18 PM, Noury Bouraqadi wrote:
Stéf,
On 11 sept. 08, at 21:32, Noury Bouraqadi wrote:
On 11 sept. 08, at 09:44, Stéphane Ducasse wrote:
Hi noury
I started to harvest your fixes and I learned something :) when most of your fixes are about extending or changing a package just publish a new version of that package. This way I can use the merge tool and be much more efficient, do not create a specific package with specific class extension for it else I have to modify everything by hand.
This sounds like a cleaner way indeed. If you didn't finish harvesting it, I can split different changes as you suggest.
Did you harvested my previous fixes ? Cause I added an extra bug fix (attached) to the class builder to avoid the creation of "zombie" classes (classes not in the SystemDictionary => Memory leak) when class variable names are lowercase. The test
BTW, where one can check to see if a package has been harvested?
Noury ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury
European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------
<fixClassVarsVarlidation-Noury12sept2008.cs> _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Noury I harvested your classBuilder fixes. For the MC related ones, could you package them separately and in a way that merge is working well Then post them in the bugtracking and that we can ask lukas or adrian to have a look? Tx
Stéf,
On 11 sept. 08, at 21:32, Noury Bouraqadi wrote:
On 11 sept. 08, at 09:44, Stéphane Ducasse wrote:
Hi noury
I started to harvest your fixes and I learned something :) when most of your fixes are about extending or changing a package just publish a new version of that package. This way I can use the merge tool and be much more efficient, do not create a specific package with specific class extension for it else I have to modify everything by hand.
This sounds like a cleaner way indeed. If you didn't finish harvesting it, I can split different changes as you suggest.
Did you harvested my previous fixes ? Cause I added an extra bug fix (attached) to the class builder to avoid the creation of "zombie" classes (classes not in the SystemDictionary => Memory leak) when class variable names are lowercase. The test
BTW, where one can check to see if a package has been harvested?
Noury ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury
European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------
<fixClassVarsVarlidation-Noury12sept2008.cs> _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I sent the wrong version of the changeset in my previous email. Attached the right one. Noury On 12 sept. 08, at 19:18, Noury Bouraqadi wrote:
Stéf,
On 11 sept. 08, at 21:32, Noury Bouraqadi wrote:
On 11 sept. 08, at 09:44, Stéphane Ducasse wrote:
Hi noury
I started to harvest your fixes and I learned something :) when most of your fixes are about extending or changing a package just publish a new version of that package. This way I can use the merge tool and be much more efficient, do not create a specific package with specific class extension for it else I have to modify everything by hand.
This sounds like a cleaner way indeed. If you didn't finish harvesting it, I can split different changes as you suggest.
Did you harvested my previous fixes ? Cause I added an extra bug fix (attached) to the class builder to avoid the creation of "zombie" classes (classes not in the SystemDictionary => Memory leak) when class variable names are lowercase. The test
BTW, where one can check to see if a package has been harvested?
Noury ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury
European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------
<fixClassVarsVarlidation-Noury12sept2008.cs>
Noury Bouraqadi ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------
participants (2)
-
Noury Bouraqadi -
Stéphane Ducasse