cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake https://pypy.org | IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end and https://libera.irclog.whitequark.org/pypy | Matti: I made a bit of progress, the tests now only segfault towards the end
the_rat_ has quit [Quit: ZNC - http://znc.in]
the_rat has joined #pypy
jcea has quit [Ping timeout: 260 seconds]
lritter has joined #pypy
otisolsen70 has joined #pypy
Atque has joined #pypy
Waynes has joined #pypy
Dejan has joined #pypy
Waynes has quit [Quit: Leaving.]
Techcable has quit [Ping timeout: 244 seconds]
<fijal> LarstiQ: how do you do complex project development that breaks stuff?
<fijal> like, a big refactoring
Dejan has quit [Ping timeout: 244 seconds]
Dejan has joined #pypy
Atque has quit [Quit: ...]
<LarstiQ> fijal: rebasing
<LarstiQ> which is more annoying than merging if upstream has changed, so try not to have anything big that can't be merged piecemeal
<fijal> well, so I think that answers the question - many workflows around current business models just don't allow big refactorings
<fijal> I find it mindboggling, but it seems to be prevalent
<fijal> ok, once you rebased, how do you find out all the checkins that were on that branch?
Dejan_ has joined #pypy
Dejan has quit [Read error: Connection reset by peer]
Atque has joined #pypy
Dejan_ has quit [Quit: Leaving]
Dejan has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Atque has quit [Quit: ...]
jcea has joined #pypy
Atque has joined #pypy
Atque has quit [Ping timeout: 258 seconds]
jcea has quit [Ping timeout: 268 seconds]
Atque has joined #pypy
epony has quit [Remote host closed the connection]
lritter has quit [Quit: Leaving]
Techcable has joined #pypy
greedom has joined #pypy
Dejan has quit [Quit: Leaving]
Atque has quit [Ping timeout: 258 seconds]
Atque has joined #pypy
greedom has quit [Remote host closed the connection]
otisolsen70 has quit [Quit: Leaving]