Date: Wed, 21 Feb 2018 20:14:05 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: freebsd-current@freebsd.org Subject: Re: A small procedural request Message-ID: <20180221201405.4c0b1262e2f239616120869a@dec.sakura.ne.jp> In-Reply-To: <1ec9ccb4-0f0e-e525-4ce8-71d9d34172ae@freebsd.org> References: <1ec9ccb4-0f0e-e525-4ce8-71d9d34172ae@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi. +1. But have one suggestion for format. Something like Broken by: rXXXXXXX Broken by: Unknown (Bugfix but the revision introduced it is unknown) and optionally Broken by: No (To emphasize it's NOT a bugfix.) would be better for scripts already handling "MFC after: " or "X-MFC-With: " etc. to support this. If put on the top with "MFC rXXXXXX: Comments", it can be FIX rXXXXXX: Comments or for multiple revisions, FIX rXXXXXX rYYYYYY rZZZZZZ: Comments for multiple individuals FIX rXXXXXX-rYYYYYY: Comments for massive continuous range would be better. Regards. On Wed, 21 Feb 2018 12:01:33 +0800 Julian Elischer <julian@freebsd.org> wrote: > Hi,〓 I have a very small request to those committing into head. > > If you commit a fix, then if it is possible to easily do so, can you > give the revision number in which the regression was introduced? > > like "this was〓 broken in r329xxx" > > this allows people who are looking for specific problems to say "Ok > that bug was introduced after the snapshot I'm working on and can't be > my issue". > > (we are not always working on the very tip). > > > thanks > > Julian > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180221201405.4c0b1262e2f239616120869a>