From: Michael 'veremitz' Everitt <gentoo@veremit.xyz>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] package.deprecated: Create initial template
Date: Fri, 6 Dec 2019 15:46:43 +0000 [thread overview]
Message-ID: <8ff88744-8316-b89a-f577-ad7766defa83@veremit.xyz> (raw)
In-Reply-To: <CAEdQ38FUNfQhT08JAd=z0QkxeHQUOVpZn2=P=raaYovkrUDZVg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1040 bytes --]
On 06/12/19 15:41, Matt Turner wrote:
> On Fri, Dec 6, 2019 at 5:51 AM Alexis Ballier <aballier@gentoo.org> wrote:
>> On Fri, 6 Dec 2019 04:33:36 -0500
>> Tim Harder <radhermit@gentoo.org> wrote:
>>
>>> On 2019-12-06 Fri 04:03, Alexis Ballier wrote:
>>>> it's not just like repoman and cvs since repoman commit did push ;)
>>>> it will never be perfect but i really like repoman commit to refuse
>>>> to even commit if there's something obviously wrong
>>> I'm more of the opinion (and am working towards that practicality in
>>> terms of runtime speed) that a subset of QA checks should be run as a
>>> git hook which would cause push failures on certain classes of bad
>>> commits.
>>
>> There should be both. Amending the 23rd commit message because one
>> mistyped a semicolon is kind of a PITA.
> It is?
>
> git rebase -i HEAD~23
>
> Is that what you think is a pain in the ass, or do you not know about
> interactive rebase? :)
>
I hope you're not suggesting a rebase of any sort in gentoo.git, Matt .... ;)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2019-12-06 15:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 16:09 [gentoo-dev] [PATCH] package.deprecated: Create initial template Michał Górny
2019-12-05 16:36 ` Alexis Ballier
2019-12-05 16:53 ` William Hubbs
2019-12-05 17:11 ` Alexis Ballier
2019-12-07 10:34 ` Joonas Niilola
2019-12-05 17:39 ` Michał Górny
2019-12-05 17:59 ` Alexis Ballier
2019-12-05 18:04 ` Michał Górny
2019-12-05 19:12 ` Gerion Entrup
2019-12-05 22:00 ` Alexis Ballier
2019-12-06 8:23 ` Tim Harder
2019-12-06 9:03 ` Alexis Ballier
2019-12-06 9:33 ` Tim Harder
2019-12-06 10:50 ` Alexis Ballier
2019-12-06 15:41 ` Matt Turner
2019-12-06 15:46 ` Michael 'veremitz' Everitt [this message]
2019-12-06 16:28 ` Mike Gilbert
2019-12-06 17:57 ` Michael 'veremitz' Everitt
2019-12-06 16:29 ` Alexis Ballier
2019-12-06 17:58 ` Michael Orlitzky
2019-12-07 9:38 ` Kent Fredric
2019-12-07 9:46 ` Kent Fredric
2019-12-06 11:33 ` Michał Górny
2019-12-06 11:45 ` Tim Harder
2019-12-05 16:39 ` Andreas K. Huettel
2019-12-05 16:46 ` Matt Turner
2019-12-05 17:56 ` Mikle Kolyada
2019-12-05 19:01 ` Alec Warner
2019-12-05 23:37 ` Aaron Bauman
2019-12-06 0:36 ` Chí-Thanh Christopher Nguyễn
2019-12-06 7:15 ` Michał Górny
2019-12-06 7:35 ` Tim Harder
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=8ff88744-8316-b89a-f577-ad7766defa83@veremit.xyz \
--to=gentoo@veremit.xyz \
--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