[core-workflow] Re: Adding some concrete examples to the NEWS entry guide?

Having examples in the templates could instill more consistency and hopefully prevent errors as my first attempt failed (did not like bpo- in the first (summary) line. Do not forget clear instructions for when you cannot, for whatever reason, use blurb add. Sent from my iPhoneTenzij hierboven

[core-workflow] Re: Adding some concrete examples to the NEWS entry guide?

2017-11-27 16:29 GMT+01:00 Berker Peksağ : > thanks.rust-lang.org basically dumps all author names without giving > zero context. Contributor A might just a fix a typo or contribute a > non-trivial feature. There is no way to figure it out without doing > some research. >

[core-workflow] Re: Adding some concrete examples to the NEWS entry guide?

On Mon, Nov 27, 2017 at 2:10 PM, Victor Stinner wrote: > "Patch by" was useful with Mercurial which didn't allow to store an > author and a committer. Git now stores the author and the committer: > > vstinner@apu$ git show --pretty=full >

[core-workflow] Re: Adding some concrete examples to the NEWS entry guide?

"Patch by" was useful with Mercurial which didn't allow to store an author and a committer. Git now stores the author and the committer: vstinner@apu$ git show --pretty=full 5b48dc638b7405fd9bde4d854bf477dfeaaddf44 --stat commit 5b48dc638b7405fd9bde4d854bf477dfeaaddf44 Author: Jonas Haag

[core-workflow] Re: Adding some concrete examples to the NEWS entry guide?

+1. Related question: Should the news entry include "Patch by ?". I noticed some entries have this, some don't. Is there a rule? Thanks. ___ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to