Smalltalk › Squeak › Squeak - Dev

Commit messages revisited

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

25 messages Options

bpi

Re: Commit messages revisited

Am 23.10.2009 um 05:06 schrieb Ronald Spengler:

> Two things:
>
> - I like to see what (for example,) Nicholas has just done in the
> trunk *in the context of the broader dialog.* Context is everything.
>
> - I got a very warm fuzzy feeling knowing that there were lots of
> eyes on what I was doing when I put changes to Compiler into the inbox
> when I was removing the old colorPrint feature. One of the things that
> makes this community epic is the level of peer review and feedback
> that I get; if I've done something stupid, I'm learning about it from
> you almost right away. In a digest, I think I'd lose some of that.

+1

I think that is another great reason why commit messages are a good
thing in my opinion.

Cheers,
Bernhard

Ken G. Brown

code execution visualization?

In reply to this post by hernanmd

What's the best way to trace and log the execution path of a running system in order to understand what parts are getting touched?

eg. When Monticello 1.6 is loading trunk

Are there any visualization tools that would show that in a visual form?

Thx for any tips.
Ken G. Brown

hernanmd

Re: Commit messages revisited

In reply to this post by Igor Stasenko

2009/10/23 Igor Stasenko <[hidden email]>

2009/10/22 Hernán Morales Durand <[hidden email]>:

> Please, set up another list for commit messages, as Laurence said the
> mailing list is for programming in/using Squeak, not for developing
> the Squeak itself. There are many options before expecting/requiring
> 1000+ subscribers to create filtering rules in their e-mail clients.
> Cheers,
>

Is developing Squeak implying using and programming in Squeak?

If yes, why there is a separate mailing list for the vm?

Cheers,

Hernán

Igor Stasenko

Re: Commit messages revisited

2009/10/25 Hernán Morales Durand <[hidden email]>:

>
>
> 2009/10/23 Igor Stasenko <[hidden email]>
>>
>> 2009/10/22 Hernán Morales Durand <[hidden email]>:
>> > Please, set up another list for commit messages, as Laurence said the
>> > mailing list is for programming in/using Squeak, not for developing
>> > the Squeak itself. There are many options before expecting/requiring
>> > 1000+ subscribers to create filtering rules in their e-mail clients.
>> > Cheers,
>> >
>>
>> Is developing Squeak implying using and programming in Squeak?
>
> If yes, why there is a separate mailing list for the vm?
>

Mind , if i don't answer this question? I don't know. :)

P.S. I'm fed up with this topic. I prefer to discuss the technical
issue in this list, ideas and innovations, instead of endless debates,
whether its good or bad to have bot postings to list.
Regardless what we choose, this will not improve the quality of
software nor add new features to it.

> Cheers,
>
> Hernán
>

--
Best regards,
Igor Stasenko AKA sig.

Andreas.Raab

Re: Commit messages revisited

In reply to this post by hernanmd

Hernán Morales Durand wrote:

> 2009/10/23 Igor Stasenko <[hidden email] <mailto:[hidden email]>>
>
> 2009/10/22 Hernán Morales Durand <[hidden email]
> <mailto:[hidden email]>>:
> > Please, set up another list for commit messages, as Laurence said the
> > mailing list is for programming in/using Squeak, not for developing
> > the Squeak itself. There are many options before expecting/requiring
> > 1000+ subscribers to create filtering rules in their e-mail clients.
> > Cheers,
> >
>
> Is developing Squeak implying using and programming in Squeak?
>
> If yes, why there is a separate mailing list for the vm?

Because there's enough interest to keep it alive. If there wasn't, the
discussions would've moved here a long time ago.

Cheers,
- Andreas