| 1 |
[2019-06-27 08:49:59+0100] Michael Everitt: |
| 2 |
> On 27/06/19 08:42, Haelwenn (lanodan) Monnier wrote: |
| 3 |
> > Github wants me to send them a full update of the gentoo tree everytime and |
| 4 |
> > apparently doesn't like shallow clones. |
| 5 |
> > |
| 6 |
> > ! [remote rejected] revbump/app-misc_g810-led/0.3.5 -> revbump/app-misc_g810-led/0.3.5 (shallow update not allowed) |
| 7 |
> > |
| 8 |
> > So I'm trying to send this simple version bump via git send-email instead. |
| 9 |
> |
| 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 |
|
| 14 |
Well, this branch is recent enough to not need a rebase as I did it |
| 15 |
directly from the master branch of the gentoo repo. |
| 16 |
|
| 17 |
I think the only way I had it working nicely (with still wasting a |
| 18 |
pile of bandwith/time on sending gentoo commits to github), was with |
| 19 |
cloning from my Github Fork™ and add the gentoo repo as a remote. |
| 20 |
|
| 21 |
-- |
| 22 |
Haelwenn (lanodan) Monnier |
Archives