On Mon, Oct 24, 2016 at 10:29:30PM +0100, Dominik Vogt wrote: > On Sun, Oct 23, 2016 at 02:46:46AM +0100, Dominik Vogt wrote: > > On Sat, Oct 22, 2016 at 06:32:12PM -0700, GitHub wrote: > > > Branch: refs/heads/ta/reluctant-news > > > Home: https://github.com/fvwmorg/fvwm > > > Commit: 64d4244746754610a64ed35de9ca69e557d3e25a > > > > > > https://github.com/fvwmorg/fvwm/commit/64d4244746754610a64ed35de9ca69e557d3e25a > > > Author: Thomas Adam <tho...@xteddy.org> > > > Date: 2016-10-23 (Sun, 23 Oct 2016) > > > > > > Changed paths: > > > M docs/DEVELOPERS.md > > > > > > Log Message: > > > ----------- > > > DEVELOPERS: mention NEWS file > > > > Thanks. > > > > > Let's try and get patches which introduce changes to also include changes > > > to > > > the NEWS file. > > ... but in a separate commit please. Patching the NEWS file in > the same commit as the code change makes bug hunting and reverting > patches more difficult.
Maybe, but how often does that really happen? The problem with making NEWS file special somehow is going to cause problems with git-bisect because you'd be forever skipping over commits. -- Thomas Adam
