public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org,Michael Orlitzky <mjo@gentoo.org>
Subject: Re: [gentoo-dev] [RFC pre-GLEP] Gentoo Git Workflow
Date: Tue, 25 Jul 2017 13:52:54 +0200	[thread overview]
Message-ID: <0A428688-D128-4767-A9E5-E0F2D3004B18@gentoo.org> (raw)
In-Reply-To: <d7063459-69ab-e921-e240-2ab7a6fad40f@gentoo.org>

Dnia 25 lipca 2017 13:25:38 CEST, Michael Orlitzky <mjo@gentoo.org> napisał(a):
>On 07/25/2017 04:05 AM, Michał Górny wrote:
>> 
>> Here's the current draft:
>> https://wiki.gentoo.org/wiki/User:MGorny/GLEP:Git
>> 
>
>It's mostly fine, but there are two changes I disagree with:
>
>> When doing one or more changes that require a revision bump, bump the
>> revision in the commit including the first change. Split the changes
>> into multiple logical commits without further revision bumps — since
>> they are going to be pushed in a single push, the user will not be
>> exposed to interim state.
>
>We shouldn't play games in the repo and hope that everything works out
>if we wait to push until just the right time. We're not going to run
>out
>of numbers -- it's simpler and more correct to do a new revision with
>each commit.

I have no clue what you mean. I'm just saying that if you push 10 changes in 10 commits, you don't have to go straight to -r10 in a single push.

>
>
>> Gentoo developers are still frequently using Gentoo-Bug tag,
>> sometimes followed by Gentoo-Bug-URL. Using both simultaneously is
>> meaningless (they are redundant), and using the former has no
>> advantages over using the classic #nnnnnn form in the summary or the
>> body.
>
>There are two main advantages over having the bug number in the
>summary.
>Space is at a premium in the summary, as Tobias pointed out, and the
>
>  Gentoo-Bug: whatever
>
>format is trivially machine-readable, whereas sticking it somewhere
>else
>is less so.

Except that there is no machines using it. In all contexts, using full URL for machine readability is better as it works with all software out of the box.

>
>And just a reminder -- Gokturk worked to get a lot of this stuff into
>the devmanual, e.g.
>
>  https://devmanual.gentoo.org/ebuild-maintenance/index.html
>
>Some of that is important, like the warning not to use "bug #x" in the
>body of the commit message.


-- 
Best regards,
Michał Górny (by phone)


  reply	other threads:[~2017-07-25 11:53 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 [this message]
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 ` [gentoo-dev] " Andreas K. Huettel
2017-09-08 21:19 ` 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=0A428688-D128-4767-A9E5-E0F2D3004B18@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mjo@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