GNU bug report logs - #43117
[PATCH] Add .git-blame-ignore-revs file

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: larsi <at> gnus.org, dgutov <at> yandex.ru, rpluim <at> gmail.com, leungbk <at> mailfence.com, 43117 <at> debbugs.gnu.org
Subject: bug#43117: [PATCH] Add .git-blame-ignore-revs file
Date: Sun, 18 Oct 2020 20:59:41 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Sun, 18 Oct 2020 10:54:02 -0700
> Cc: leungbk <at> mailfence.com, larsi <at> gnus.org, rpluim <at> gmail.com, 
> 	43117 <at> debbugs.gnu.org, dgutov <at> yandex.ru
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > I don't think I understand what does this file mean from the
> > maintenance POV.  Who will maintain it, and what are the procedures?
> 
> I would propose that we treat it as an optional feature rather than
> striving for it to include a complete list of all "uninteresting"
> commits at all times.
> 
> Even if it were to include only a proportion of some of the latest
> "uninteresting" cleanups, that could already be of help.  When someone
> stumbles into a commit that gets in the way of their git blaming they
> could also consider adding it.

We already mark such commits with a leading semi-colon.  Will this
file simply repeat those commits?

> > And what should be done about it while merging from the release branch
> > to master?
> 
> I don't think anything in particular needs doing, since the sha-1 will
> stay the same after a merge.  Or am I missing something?

Not all of the commits get merged.  Some are skipped.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.