Adrien,

You might prefer gnucash-patches. gnucash-changes includes the code diff while 
gnucash-patches has just the commit message. Both link to the commit on GitHub 
so if you feel a need to look at a patch it's only a click away.

Like gnucash-announce those are send-only lists. They don't accept posts from 
subscribers. If you want to comment on a commit you'll need a GitHub account.

Those lists reflect only commits to the repositories. You'll have to monitor 
https://github.com/Gnucash/gnucash/pulls to keep up with work in progress. 
Github publishes an RSS feed on the page.

Regards,
John Ralls


> On Sep 20, 2020, at 10:54 PM, Adrien Monteleone 
> <adrien.montele...@lusfiber.net> wrote:
> 
> Thanks Christopher, I didn't know that list existed.
> 
> Note to anyone using Gmane, it is not offered there, so regular mail client 
> only. (at least for now)
> 
> Regards,
> Adrien
> 
> On 9/18/20 6:05 AM, Christopher Lam wrote:
>> A small note about code progress (and occasional regressions). Development
>> takes place mainly via github and IRC; I'd wager most subscribers to devel
>> *will* have enough understanding to understand the ongoing discussions and
>> changes. Even if they have little coding skills, the commit messages will
>> almost always contain adequate detail regarding changes. Commit messages
>> are generated and distributed live to any subscriber at
>> https://lists.gnucash.org/mailman/listinfo/gnucash-changes
> 
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to