[Vm-dev] Commit process

Eliot Miranda eliot.miranda at gmail.com
Thu Mar 8 16:03:26 UTC 2018


Hi Alistair,

> On Mar 8, 2018, at 7:34 AM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> 
> Hi Sean,
> 
> 
>> On Mar 8, 2018, at 6:06 AM, Sean P. DeNigris <sean at clipperadams.com> wrote:
>> 
>> 
>> Hi guys, forgive my potentially naive intrusion, but I've noticed a lot of
>> git commits which seem like noise. When I make commits like these - e.g.
>> tweaking tiny details to pacify CI - I call it "programming by flopping
>> around" ha ha. Anyway, as I've recently learned, a great practice is to
>> perform these on another branch until things are working, and then squash
>> all the commits into one before merging - usually pretty easy with git. That
>> having been said, I know very little about the VM dev process, so if none of
>> this applies, feel free to consider me a crazy old man mumbling things on
>> the street corner to passersby ;)
> 
> Those commits were on a branch.  I agree that it's best not to push after each commit.  The emails however confused me too.  Is it possible for the commit emails to clearly state the branch name?

Sorry.  I meant yo say the title of the emails.  In Tobias' defence, if one is working on the CI then, without a lot of effort, one has no choice other than to commit so that the CI can pull and do its thang.  Perhaps turning off the notifications for certain branches is possible?

> 
>> 
>> 
>> 
>> -----
>> Cheers,
>> Sean
>> --
>> Sent from: http://forum.world.st/Squeak-VM-f104410.html


More information about the Vm-dev mailing list