From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC pre-GLEP] Gentoo Git Workflow
Date: Fri, 28 Jul 2017 12:38:26 +0200 [thread overview]
Message-ID: <1596428.S6uqz0IeBJ@porto> (raw)
In-Reply-To: <1500969906.1206.1.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2481 bytes --]
Am Dienstag, 25. Juli 2017, 10:05:06 CEST schrieb Michał Górny:
> Hi, everyone.
>
> There have been multiple attempts at grasping this but none so far
> resulted in something official and indisputable. At the same time, we
> end having to point our users at semi-official guides which change
> in unpredictable ways.
>
> Here's the current draft:
> https://wiki.gentoo.org/wiki/User:MGorny/GLEP:Git
>
> The basic idea is that the GLEP provides basic guidelines for using git,
> and then we write a proper manual on top of it (right now, all the pages
> about it end up as a mix of requirements and a partial git manual).
>
> What do you think about it? Is there anything else that needs being
> covered?
TL;DR: I like it; minor comments on the commit message format (surprise). We
should strive to provide consistent standards for it.
> ===Commit messages===
[...]
> If a bug is associated
> with a change, then it should be included in the summary line as
> <kbd>#nnnnnn</kbd> or likewise.
..., for practical reasons in a format that is recognized by willikins.
So, please DON'T do "... fixes #234987".
I suggest we recommend a plain "... bug 234567 ..."
So far, "bug x" in our repository by default refers to the Gentoo bugzilla,
and it makes sense to stick with that.
> The tag part is included in the full commit log as an extension to the
> body. It consists of one or more lines consisting of key, followed by a
> colon and a space, followed by value. Git does not enforce any
> standardization of the keys, and the tag format is ''not'' meant for
> machine processing.
>
> A few tags of common use are:
[...]
> ** <kbd>Bug: <nowiki>https://bugs.gentoo.org/NNNNNN</nowiki></kbd>; — to
> reference a bug,
> ** <kbd>Closes: <nowiki>https://github.com/gentoo/gentoo/pull/NNNN</nowi
> ki></kbd>; — to automatically close a GitHub pull request,
> ** <kbd>Fixes: <nowiki>https://bugs.gentoo.org/NNNNNN</nowiki></kbd>; —
> to indicate a fixed bug,
I would like to suggest that *if* such tags are used, we require that they
should always contain a full URL to an issue tracker or code source.
This allows generic referencing of other bug trackers, leaves developers the
option to auto-handle github-specific things, and still (for the purists)
doesn't require mentioning Github in the GLEP.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-28 10:38 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 8:05 [gentoo-dev] [RFC pre-GLEP] Gentoo Git Workflow Michał Górny
2017-07-25 8:23 ` Nicolas Bock
2017-07-25 8:49 ` Dirkjan Ochtman
2017-07-25 10:59 ` Tobias Klausmann
2017-07-25 11:49 ` Michał Górny
2017-07-25 11:25 ` Michael Orlitzky
2017-07-25 11:52 ` Michał Górny
2017-07-25 12:26 ` Michael Orlitzky
2017-07-25 13:23 ` Michał Górny
2017-07-25 16:12 ` Michael Orlitzky
2017-07-25 20:29 ` Mike Gilbert
2017-07-25 20:31 ` Michael Orlitzky
2017-07-25 20:55 ` Michał Górny
2017-07-25 22:26 ` Rich Freeman
2017-07-25 22:30 ` Michał Górny
2017-07-25 22:46 ` Rich Freeman
2017-07-25 22:50 ` Michał Górny
2017-07-25 13:26 ` Rich Freeman
2017-07-25 13:48 ` Michał Górny
2017-07-26 9:21 ` Ulrich Mueller
2017-07-26 17:04 ` Kristian Fiskerstrand
2017-07-26 17:20 ` Rich Freeman
2017-07-26 17:32 ` Kristian Fiskerstrand
2017-07-27 9:54 ` Kristian Fiskerstrand
2017-07-26 17:00 ` Kristian Fiskerstrand
2017-07-25 11:50 ` Jonas Stein
2017-07-25 12:28 ` [gentoo-dev] " Michael Palimaka
2017-07-25 13:36 ` Michał Górny
2017-07-26 17:05 ` Kristian Fiskerstrand
2017-07-26 22:20 ` Sam Jorna
2017-07-27 6:08 ` Daniel Campbell
2017-07-27 13:48 ` Michał Górny
2017-07-25 12:54 ` [gentoo-dev] " Joshua Kinard
2017-07-25 13:43 ` Michał Górny
2017-07-26 13:41 ` Brian Evans
2017-07-26 17:17 ` Kristian Fiskerstrand
2017-07-27 13:52 ` Michał Górny
2017-07-27 13:54 ` Kristian Fiskerstrand
2017-07-27 13:58 ` Michał Górny
2017-07-27 14:08 ` Kristian Fiskerstrand
2017-07-27 14:11 ` Michał Górny
2017-07-27 14:25 ` Kristian Fiskerstrand
2017-07-27 22:00 ` [gentoo-dev] " Duncan
2017-07-27 22:37 ` Duncan
2017-07-27 23:12 ` Duncan
2017-07-27 23:38 ` Duncan
2017-07-28 0:15 ` Duncan
2017-07-28 10:38 ` Andreas K. Huettel [this message]
2017-09-08 21:19 ` [gentoo-dev] " Rich Freeman
2017-09-09 0:00 ` Kristian Fiskerstrand
2017-09-09 7:47 ` Michał Górny
2017-09-09 9:29 ` Rich Freeman
2017-09-10 7:39 ` Daniel Campbell
2017-09-10 9:34 ` Michał Górny
2017-09-10 22:13 ` Daniel Campbell
2017-09-11 3:09 ` Dean Stephens
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=1596428.S6uqz0IeBJ@porto \
--to=dilfridge@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