<alyssa>
I.e. note to self, we're supposed to be 128-aligning the metadata_size (I guess they call it the header)
ric96 has quit [*.net *.split]
Elpaulo has quit [Quit: Elpaulo]
stikonas has joined #panfrost
* hanetzer
winks with both eys
raster has joined #panfrost
ric96 has joined #panfrost
_whitelogger has joined #panfrost
_whitelogger has joined #panfrost
stikonas has quit [Remote host closed the connection]
raster has quit [Remote host closed the connection]
<alyssa>
...How do I download patches off an ML...?
<alyssa>
mutt
<ente>
patch(1) strips anything before --- filename
<ente>
so if you have the mails already, you can just use git apply or patch(1)?
<alyssa>
_download_
<ente>
if you don't, mailman sometimes has mailing list archives available in mbox format
<ente>
figured because you said mutt you already have the mails, sorry
<ente>
in mlmmj you can send a request for an individual mail to listname+get-1234@lists.example.com and it resends the message to you. might be possible with majordomo or mailman too.
<ente>
actually I've been wondering myself how I can mirror mailing list archives, since gmane/mail-archive.com/... are going out of order one after another
<ente>
easiest way imo: get the list archive forwarded by someone who has the entire list :)
<alyssa>
tomeu: You know, I've been trying to push your patches all morning... I think this is a sign nondrm support should be dropped ASAP :P
<alyssa>
Upon second thought, I'm just squashing the series.
<alyssa>
tomeu: I squashed 2-8 to preserve bisectability without losing my sanity, but it's all pushed. nice!
BenG83 has joined #panfrost
<ezequielg>
alyssa: if patches are in patchwork, I strongly suggest you use git-pw.
Elpaulo has quit [Quit: Elpaulo]
<alyssa>
ezequielg: That requires a patchwork account
<alyssa>
No?
BenG83 has quit [Client Quit]
<ezequielg>
it might, i guess.
<ezequielg>
not too problematic. and hugely useful if you start picking patches oftenly.
<ezequielg>
specially with new patchwork, which allows to pick series.
BenG83 has joined #panfrost
<alyssa>
Also kdJSGsjafgdashkj
<alyssa>
Why is git-am such a pain
<alyssa>
This is not okay
<ezequielg>
pain how?
<ezequielg>
i think most developers (including myself) forget to state clearly where patches apply. without a clear base, applying patches is a pain, git-am or not.
<alyssa>
I don't get how to deal with conflicts
<alyssa>
And now I just tried to merge and that worked but now I have a merge commit and mesa says that's strictly wrong
<alyssa>
I have written 0 code today and all I managed to do is fight with git for hours
<ezequielg>
git am (conflicts) then git apply --reject, you fix manually and add, and then git am --cont.
<ezequielg>
painful but it is what it is
<alyssa>
?
<ezequielg>
that is how you deal with conflicts: git am and then git apply --reject
<ezequielg>
to get rid of a merge commit, git rebase and then deal again with the same conflicts.
<ezequielg>
painful, yes, welcome to our daily world.
<alyssa>
What the heck I thought I /quit'd this
<alyssa>
I guess I need to wack the bouncer
<alyssa>
Regardless, I will not be solving this. Somebody else can merge my patches on the mailing list. I don't want to play maintaininer; I just want to write code. That's not too much to ask for, though then again, but it is.