Gentoo Archives: gentoo-proxy-maint

From: Michael Everitt <m.j.everitt@×××.org>
To: gentoo-proxy-maint@l.g.o
Subject: Re: [gentoo-proxy-maint] app-misc/g810-led: Clean version bump to 0.3.5
Date: Thu, 27 Jun 2019 08:10:38
Message-Id: 0fcb84c8-efac-d46b-9778-40a5fbb9e097@iee.org
In Reply to: Re: [gentoo-proxy-maint] app-misc/g810-led: Clean version bump to 0.3.5 by "Haelwenn (lanodan) Monnier"
1 On 27/06/19 09:01, Haelwenn (lanodan) Monnier wrote:
2 > [2019-06-27 08:49:59+0100] Michael Everitt:
3 >> On 27/06/19 08:42, Haelwenn (lanodan) Monnier wrote:
4 >>> Github wants me to send them a full update of the gentoo tree everytime and
5 >>> apparently doesn't like shallow clones.
6 >>>
7 >>> ! [remote rejected] revbump/app-misc_g810-led/0.3.5 -> revbump/app-misc_g810-led/0.3.5 (shallow update not allowed)
8 >>>
9 >>> So I'm trying to send this simple version bump via git send-email instead.
10 >> It's standard practice at Gentoo to rebase your changes on the current HEAD
11 >> - it might seem perverse at first, but if you keep a clean branch in your
12 >> fork, it's not too hard to do.
13 > Well, this branch is recent enough to not need a rebase as I did it
14 > directly from the master branch of the gentoo repo.
15 >
16 > I think the only way I had it working nicely (with still wasting a
17 > pile of bandwith/time on sending gentoo commits to github), was with
18 > cloning from my Github Fork™ and add the gentoo repo as a remote.
19 >
20 you should be able to push to your Fork, and then github will prompt you to
21 make a pull-request from there. I use gentoo as a remote, to pull into my
22 'upstream'/gentoo branch (of my fork). If that makes sense?! :)

Attachments

File name MIME type
signature.asc application/pgp-signature