Anyways, in that case.. I got someone to `pass on the torch` to ... 🤣
2019-04-09 09912, 2019
anshuman73
looking forward to it :smirk:
2019-04-09 09903, 2019
code_master5
anshuman73: Hey you participated in code-in earlier.. If I remember!?? 🤔
2019-04-09 09915, 2019
anshuman73
code_master5: yep, I did. Worked on CB mostly then too
2019-04-09 09930, 2019
code_master5
Oh! And the results?
2019-04-09 09941, 2019
anshuman73
late 2016, I'm surprised you remember ! Don't remember seeing you around much at that time I think
2019-04-09 09956, 2019
anshuman73
code_master5: I was a winner from MeB :)
2019-04-09 09918, 2019
code_master5
anshuman73: Wow! congrats.. 👏 I'm lates 😅
2019-04-09 09921, 2019
code_master5
*late
2019-04-09 09958, 2019
anshuman73
late as in term of participating for GCI ?
2019-04-09 09914, 2019
code_master5
late for congratulating..
2019-04-09 09950, 2019
anshuman73
code_master5: ah 😂
2019-04-09 09919, 2019
anshuman73
someone found a backdoor for submitting proposals on #gsoc lmao
2019-04-09 09938, 2019
code_master5
anshuman73: In case you thinking how I r emember you,.. actually, I'm a close friend of ferbncode and iliekcomputers ... And I used to have a look at how their work was going on with MeB..
2019-04-09 09939, 2019
Gazooo has quit
2019-04-09 09958, 2019
code_master5
So I remember.. they mentioned you quite a few times
I just like having a merge commit since it provides context (links to the PR) and makes it easier to revert if necessary
2019-04-09 09955, 2019
reosarevok
Ok :)
2019-04-09 09938, 2019
alastairp
I like merge commits too
2019-04-09 09908, 2019
alastairp
but if it turns out to be a ff (because there have been no other commits since that PR was started), then I don't force a merge
2019-04-09 09905, 2019
alastairp
and I'll occasionally suggest that a contributor squash some of their PR if there's a stupid number of commits, and we often ask them to rebase agains master if it takes me months and months to get to reviewing it and it potentially has merge conflicts
2019-04-09 09903, 2019
reosarevok
I often rebase against master anyway every time I change something in a PR, even if there's no conflicts, because why not
2019-04-09 09909, 2019
reosarevok
(is there a why not?)
2019-04-09 09941, 2019
alastairp
I guess it makes it more possible that you'll get a ff instead of a merge commit
2019-04-09 09901, 2019
rdswift has quit
2019-04-09 09913, 2019
alastairp
a possible why-not is if someone else made a really important change, and they want to deal with any potential merge conflicts themselves because they don't trust you
2019-04-09 09930, 2019
alastairp
(not saying anything about your merging skills there...)
Heh, JSON LD issues. Will have to check that tomorrow then :)
2019-04-09 09925, 2019
aidanlw17 joined the channel
2019-04-09 09909, 2019
aidanlw17 has quit
2019-04-09 09958, 2019
aliamo joined the channel
2019-04-09 09910, 2019
aliamo has quit
2019-04-09 09919, 2019
aliamo joined the channel
2019-04-09 09904, 2019
madmouser1_ has quit
2019-04-09 09932, 2019
madmouser1_ joined the channel
2019-04-09 09954, 2019
alastairp
Mr_Monkey: wow, that double ipa really is something
2019-04-09 09913, 2019
aidanlw17 joined the channel
2019-04-09 09901, 2019
letaiv joined the channel
2019-04-09 09912, 2019
ferbncode has quit
2019-04-09 09907, 2019
rdswift
<reosarevok> With that name, I'd expect a bunch of materials sent to the press... Yeah, perhaps not the best name. That's what people called it when it was discussed. I'm okay with a different name. The intent was for things like original digital artwork which may have been used for printing covers and such.
2019-04-09 09950, 2019
rdswift
For example, the original artwork may be square, but was cropped for a gatefold cover or what not. That would currently be disallowed because it didn't exactly match the format of the release. Not sure if it would be accepted as "other".
