jaeger changed the topic of #crux-arm to: CRUX-ARM 3.7 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-7 | Logs: https://libera.irclog.whitequark.org/crux-arm/
dim44 has quit [Remote host closed the connection]
dim44 has joined #crux-arm
dim44 has joined #crux-arm
dim44 has quit [Changing host]
<r0ni> so what my script orig had done is used a local re-pack of the sarpi rpi kernel sources... i had a revelation i should fork the rpi kernel repo and tag/make releases my damn self since they don't tag any of them
<r0ni> this is my first tag lol yay
<r0ni> now i'll have to change my script for this url and tarball etc but much better than hosting a repack tarball
<r0ni> i dunno if i even tagged it right anyway... ugh i hate their repo already
<r0ni> github hates me, i can pull the repo from that commit, but it won't let me tag that commit nor release that commit, and it can't even find it when i search it. i hate github. hate.
<r0ni> alright, it looks like they sync with upstream linux and then re-merge all their changes... ugh this'll be the fastest I ever deleted a repo. maybe i'll keep it to tag releases with. still messy
<r0ni> it's past my bedtime... no more play, it's a workday ;(
<jaeger> Sounds like a bit of a pain
iamzim has joined #crux-arm
iamzim has left #crux-arm [#crux-arm]
<pitillo> I can't help in that, my bad
<pitillo> is not possible to use GH hooks in any way on your repo? I mean, something that parses a commit message to pack kernel sources? I haven't a deep knowledge about it and that canbbe a crazy idea.... discard the comment ifnit is xD
<beerman> r0ni what did you do to tag? usually it suffices to checkout a specific commit hash if you want to add a tag at a certain spot, then use "git tag $version", then you can "git checkout master" or whatever branch you are following. then with "git push --tags" you will publish that.
<beerman> your github actions look cool, good idea to use those for a stable kernel build
<r0ni> right now it seems to me they sync the branch with kernel release then push their changes so the actual commit one wants isn't the sync commit but a later one. i'm still looking at it, for now I'll keep the fork, if anything at least i can tag release from it, unlike them
<beerman> just find the commit hash you want to settle on and use "git checkout $hash"
<r0ni> yeah, thx beerman i'll look at it after work and see which option best suites it