From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] Posting patches on this mailing list instead of using GitHub
Date: Tue, 9 Jun 2020 09:01:54 +0300 [thread overview]
Message-ID: <11bf6d0e-6dfd-7908-cf4f-a2de1d428b42@gentoo.org> (raw)
In-Reply-To: <C3BL5CGCZDAJ.1MOR99O8O1RKN@hibiki>
[-- Attachment #1.1: Type: text/plain, Size: 1838 bytes --]
On 6/8/20 11:42 AM, Robert Günzler wrote:
> I honestly think it doesn't matter so much _why_ people prefer something else
> over GH. How much are you considering to switch to yet another
> solution after all...
> And I bet even that wouldn't make everybody happy :P
I wouldn't mind switching to Gentoo-hosted alternative, that does the
same. But I imagine it'd require too much work, and why replicate
something that already exists and works well.
>
> I'm fairly new to Gentoo, so I'm actually confused that https://packages.gentoo.org
> always links to https://cgit.gentoo.org/repo/gentoo.git - I thought that
> is the "source-of-truth" place then... but patches are going into the GH
> repo. Who is actually sycing all that back to cgit then?
>
As chiitoo said, Github is just used to mirror the tree and enable
creating pull requests. Github also allows easy-to-follow review
process, and CI checks before the patch is merged. Basically you take
https://patch-diff.githubusercontent.com/raw/gentoo/gentoo/pull/16110.patch
and apply it to real git tree.
>
> In response to me asking about https://sourcehut.org, in a recent thread
> you described your workflow:
>
>
> How much value would there be for you, as a first iteration of a
> solution, to get patches on the mailing-list automatically submitted as
> a PR (done by a bot) on GH?
>
> robert
If the person posting it doesn't use Github, then reviewing the pull
request goes to vain. Unless it somehow returns the feedback to sender,
but that could get dirty real fast. We sometimes give a lot of feedback
and require fixes before it can be merged. Other than that, it's an
interesting idea, but it adds more hoops to the process and that adds
probability to have mistakes / lose the contribution on the way.
-- juippis
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 642 bytes --]
next prev parent reply other threads:[~2020-06-09 6:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 23:45 [gentoo-proxy-maint] Posting patches on this mailing list instead of using GitHub Ralph Seichter
2020-06-07 7:01 ` Joonas Niilola
2020-06-07 16:42 ` Haelwenn (lanodan) Monnier
2020-06-07 17:24 ` Ralph Seichter
2020-06-07 18:15 ` Joonas Niilola
2020-06-08 8:42 ` Robert Günzler
2020-06-08 14:41 ` Randy Barlow
2020-06-08 16:59 ` Jimi Huotari
2020-06-09 6:01 ` Joonas Niilola [this message]
2020-06-07 16:58 ` tastytea
2020-06-09 6:10 ` Joonas Niilola
2020-06-09 11:37 ` tastytea
2020-06-09 12:30 ` Michał Górny
2020-06-07 17:36 ` Ralph Seichter
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=11bf6d0e-6dfd-7908-cf4f-a2de1d428b42@gentoo.org \
--to=juippis@gentoo.org \
--cc=gentoo-proxy-maint@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