From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Summary line (was: Re: Referencing bug reports in git)
Date: Mon, 31 Aug 2015 07:53:18 -0700 [thread overview]
Message-ID: <CAAr7Pr8h0yqpm=a2cdpPBYbSSsKLv9VXz0xB+znr_aVUkn006g@mail.gmail.com> (raw)
In-Reply-To: <CAATnKFBbDFu3s59eFa5oMk-X_EN87vhXM5ULq03CC_W3747V+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]
On Tue, Aug 11, 2015 at 7:35 AM, Kent Fredric <kentfredric@gmail.com> wrote:
> On 12 August 2015 at 02:28, Ian Stakenvicius <axs@gentoo.org> wrote:
> > Stuff like 'cat/pn: version bumps', 'cat/pn: new features', 'cat/pn:
> > adjusted dependencies' are generic (and short) enough yet descriptive
> > enough to see what went on while scanning the log.
>
> I personally find those summaries a bit too terse.
>
Summaries are supposed to be terse, they are summaries ;)
>
> Mostly, because when I see "A version is bumped" I immediately expect
> to know which version the bump is to, but have to dig out the diff to
> find out.
>
>
So I thought we used to have scripts that would dig out this information
and populate them in headers?
-A
> I would also prefer, where possible, to replace "adjusted
> dependencies" to be more concise, like "include dev-perl/Foo in
> dependencies", ( though of course, apply some taste, listing more than
> 3 distinct new dependencies in the summary is execessive, treat them
> like hashtags on twitter, 1 is good, 2 is OK, 3 and you're starting to
> get crazy )
>
> > Multi-package commits are going to be more of an issue of course.. I
> > did one last night, fortunately I think I can get away with using
> > "mozilla packages" in place of cat/pn since it is a very specific set
> > of packages. Perhaps for sweeping changes like that we can use the
> > herdname or projectname or the category name (if its a particular
> > category only)?
>
> Agreed. If you need multi-package changes and you can't think of a
> good category prefix to use, the commit message should visibly
> acknowledge that its a multi-package commit of some kind, and the
> *kind* of change should be very clear.
>
> Just keep in mind really the recommendations for prefix naming are
> descriptive, not prescriptive, and interpretation and good taste need
> to be applied everywhere.
>
>
>
> --
> Kent
>
> KENTNL - https://metacpan.org/author/KENTNL
>
>
[-- Attachment #2: Type: text/html, Size: 3050 bytes --]
next prev parent reply other threads:[~2015-08-31 14:53 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439128706.40b3fd64ec9c5d6d94f0f0897740bc77622c24a1.xmw@gentoo>
2015-08-09 14:09 ` [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) hasufell
2015-08-09 14:18 ` Ian Whyman
2015-08-09 14:26 ` Dirkjan Ochtman
2015-08-09 14:38 ` hasufell
2015-08-09 14:43 ` Dirkjan Ochtman
2015-08-09 14:47 ` hasufell
2015-08-09 14:54 ` Michael Orlitzky
2015-08-09 15:03 ` Sven Vermeulen
2015-08-09 15:06 ` hasufell
2015-08-09 15:19 ` Tobias Klausmann
2015-08-09 15:30 ` hasufell
2015-08-09 15:43 ` Mike Gilbert
2015-08-09 18:49 ` Davide Pesavento
2015-08-09 23:58 ` Daniel Campbell (zlg)
2015-08-10 0:25 ` Alexandre Rostovtsev
2015-08-09 19:56 ` Michał Górny
2015-08-09 21:01 ` hasufell
2015-08-09 21:11 ` Michał Górny
2015-08-09 21:30 ` Rich Freeman
2015-08-10 0:02 ` Daniel Campbell (zlg)
2015-08-10 7:31 ` Andrew Savchenko
2015-08-09 21:44 ` Andrew Savchenko
2015-08-09 22:40 ` Michał Górny
2015-08-09 23:16 ` Andrew Savchenko
2015-08-09 23:46 ` hasufell
2015-08-10 0:05 ` Daniel Campbell (zlg)
2015-08-10 0:10 ` Kent Fredric
2015-08-10 0:51 ` [gentoo-dev] Referencing bug reports in git Ulrich Mueller
2015-08-10 1:02 ` hasufell
2015-08-10 4:29 ` [gentoo-dev] " Ryan Hill
2015-08-10 12:25 ` Duncan
2015-08-10 22:57 ` Gordon Pettey
2015-08-11 1:03 ` Duncan
2015-08-11 0:17 ` Ryan Hill
2015-08-11 1:25 ` Duncan
2015-08-11 8:57 ` Tobias Klausmann
2015-08-11 9:12 ` Kent Fredric
2015-08-11 11:49 ` Rich Freeman
2015-08-11 11:58 ` hasufell
2015-08-12 7:20 ` [gentoo-dev] Bisecting Was: " Duncan
2015-08-12 7:38 ` Jason Zaman
2015-08-12 8:42 ` [gentoo-dev] " Duncan
2015-08-11 14:28 ` [gentoo-dev] Summary line (was: Re: Referencing bug reports in git) Ian Stakenvicius
2015-08-11 14:35 ` Kent Fredric
2015-08-11 15:27 ` [gentoo-dev] Summary line Ian Stakenvicius
2015-08-31 14:53 ` Alec Warner [this message]
2015-08-31 17:33 ` [gentoo-dev] Summary line (was: Re: Referencing bug reports in git) Rich Freeman
2015-08-31 18:16 ` [gentoo-dev] Summary line Michael Orlitzky
2015-08-11 14:36 ` hasufell
2015-08-11 14:39 ` Mikle Kolyada
2015-08-10 9:45 ` [gentoo-dev] Referencing bug reports in git Chí-Thanh Christopher Nguyễn
2015-08-10 10:16 ` Ulrich Mueller
2015-08-10 13:19 ` Michał Górny
2015-08-10 14:42 ` hasufell
2015-08-10 18:44 ` Chí-Thanh Christopher Nguyễn
2015-08-10 13:11 ` [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) Michał Górny
2015-08-10 20:43 ` Andrew Savchenko
2015-08-10 21:06 ` Michał Górny
2015-08-11 6:56 ` Dmitry Yu Okunev
2015-08-11 7:12 ` Michał Górny
2015-08-11 8:34 ` Dmitry Yu Okunev
2015-08-11 0:52 ` [gentoo-dev] " Ryan Hill
2015-08-10 0:08 ` Ryan Hill
2015-08-12 10:40 ` [gentoo-dev] Re: Referencing bug reports in git hasufell
2015-08-12 15:59 ` Chí-Thanh Christopher Nguyễn
2015-08-12 16:03 ` Michał Górny
2015-08-12 16:25 ` Chí-Thanh Christopher Nguyễn
2015-08-12 16:34 ` Michał Górny
2015-08-12 16:39 ` Ian Stakenvicius
2015-08-13 5:48 ` Ryan Hill
2015-08-13 11:19 ` Ben de Groot
2015-08-13 12:13 ` Rich Freeman
2015-08-14 13:37 ` Aaron W. Swenson
2015-08-18 6:03 ` Ryan Hill
2015-08-14 20:04 ` Andrew Savchenko
2015-08-14 20:17 ` Matthias Maier
2015-08-15 7:17 ` Daniel Campbell (zlg)
2015-08-12 16:15 ` hasufell
2015-08-12 17:38 ` Matt Turner
2015-08-12 17:48 ` Dmitry Yu Okunev
2015-08-12 17:54 ` hasufell
2015-08-13 2:30 ` [gentoo-dev] " Steev Klimaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAr7Pr8h0yqpm=a2cdpPBYbSSsKLv9VXz0xB+znr_aVUkn006g@mail.gmail.com' \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox