SpellChecker has quit [Remote host closed the connection]
SpellChecker has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 258 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 260 seconds]
lightningbot has quit [Remote host closed the connection]
lightningbot has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 255 seconds]
ronoaldo has quit [Quit: Konversation terminated!]
z9z0b3t1_ has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 244 seconds]
bitdex has joined #bitcoin-core-dev
Guest53 has joined #bitcoin-core-dev
evanlinjin has joined #bitcoin-core-dev
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
mikehu44 has joined #bitcoin-core-dev
Guest53 has quit [Ping timeout: 252 seconds]
sudoforge has quit [Ping timeout: 240 seconds]
sudoforge has joined #bitcoin-core-dev
<DavidBakin>
Sometimes DrahtBot itself gives you a nice message in your PR titled "Conflicts" with a list of PRs that you should consider in relationship to your new PR. And sometimes you just get a message from Github that "DrahtBot mentioned this pull request" that points you to another PR and there's nothing there except that DrahtBot mentioned your PR over there. What's the difference?
brunoerg has joined #bitcoin-core-dev
sudoforge has quit [Ping timeout: 246 seconds]
brunoerg has quit [Ping timeout: 260 seconds]
<DavidBakin>
oh wait - it looks like DrahtBot only puts the "conflict" message in your PR once then edits it to keep it up-to-date. I didn't realize that because when it edits it its place in the comment timeline doesn't change.
mikehu44_ has joined #bitcoin-core-dev
mikehu44 has quit [Ping timeout: 246 seconds]
brunoerg has joined #bitcoin-core-dev
evanlinjin has quit [Ping timeout: 240 seconds]
mikehu44_ has quit [Ping timeout: 246 seconds]
brunoerg has quit [Ping timeout: 250 seconds]
donor_ has joined #bitcoin-core-dev
donor_ has quit [Ping timeout: 258 seconds]
Guest81 has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
ExEric3 has quit [Remote host closed the connection]
Guest81 has quit [Client Quit]
donor_ has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 244 seconds]
evanlinjin has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 258 seconds]
donor_ has quit [Ping timeout: 240 seconds]
jonatack has quit [Ping timeout: 255 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 246 seconds]
sipsorcery has joined #bitcoin-core-dev
donor_ has joined #bitcoin-core-dev
Guest45 has joined #bitcoin-core-dev
Guest45 has quit [Client Quit]
brunoerg has joined #bitcoin-core-dev
jtraub91 has quit [Quit: WeeChat 3.2]
brunoerg has quit [Ping timeout: 255 seconds]
donor_ has quit [Ping timeout: 276 seconds]
Guyver2 has joined #bitcoin-core-dev
mikehu44 has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 258 seconds]
Guyver2_ has joined #bitcoin-core-dev
mikehu44 has quit [Ping timeout: 256 seconds]
mikehu44 has joined #bitcoin-core-dev
Guyver2 has quit [Ping timeout: 246 seconds]
mikehu44 has quit [Ping timeout: 246 seconds]
mikehu44 has joined #bitcoin-core-dev
sipsorcery has quit [Ping timeout: 260 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 260 seconds]
sipsorcery has joined #bitcoin-core-dev
cameron[m] has quit [Quit: You have been kicked for being idle]
kexkey has quit [Ping timeout: 246 seconds]
kexkey has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
mikehu44_ has joined #bitcoin-core-dev
evanlinjin has quit [Ping timeout: 240 seconds]
mikehu44 has quit [Ping timeout: 256 seconds]
evanlinjin has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 255 seconds]
evanlinjin has quit [Remote host closed the connection]
evanlinjin has joined #bitcoin-core-dev
___nick___ has joined #bitcoin-core-dev
sipsorcery has quit [Remote host closed the connection]
<jamesob>
If anyone has any suggestions for additional task bounties (along the lines of existing ones here: https://nydig.com/bounties) please let me know - we're looking to add more.
furszy has quit [Remote host closed the connection]
<michaelfolkson>
Whenever I squash commits I use "fixup" rather than "squash". I generally always want to discard the commit's log message
<michaelfolkson>
Would changing the contributing guidance on squashing commits to use "fixup" rather than "squash" be an idea? Happy to open a PR if so
<sipa>
The only difference is that with squash you get prompted to combine the messages, while with fixup it's just discarded without question. Unless we want to go into the distinction between the two (which seems too detailed for the writeup there IMO), I'd say squash is the safer option to recommend.
<michaelfolkson>
Ok thanks
ronoaldo has joined #bitcoin-core-dev
<laanwj>
imo the less lossy option is preferable you can always delete something in the editor, having to re-add it is more frustrating
Guyver2_ has left #bitcoin-core-dev [#bitcoin-core-dev]
SpellChecker has quit [Remote host closed the connection]
provoostenator has quit [Quit: You have been kicked for being idle]
cmirror has quit [Ping timeout: 276 seconds]
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #25285: Add AutoFile without ser-type and ser-version and use it where possible (master...2206-autofile-🌟) https://github.com/bitcoin/bitcoin/pull/25285
<bitcoin-git>
[bitcoin] martinus opened pull request #25288: test: Reliably don't start itself in lint-all.py runs all tests twice (master...2022-06-fix-lint-all-starting-itself) https://github.com/bitcoin/bitcoin/pull/25288
z9z0b3t1_ has joined #bitcoin-core-dev
<laanwj>
hebasto: on freebsd i get the error "make[3]: illegal argument to -j -- must be positive integer!", does it maybe call hardcoded into "make" instead of what is used for the outer built ("gmake" in this case)?
jm has joined #bitcoin-core-dev
z9z0b3t1c has quit [Ping timeout: 244 seconds]
<laanwj>
i also get an error about not being able to find a boost header at make time
sipsorcery has quit [Ping timeout: 248 seconds]
ExEric3 has joined #bitcoin-core-dev
sipsorcery has joined #bitcoin-core-dev
ExEric3 has quit [Remote host closed the connection]
ExEric3 has joined #bitcoin-core-dev
Aaronvan_ has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 244 seconds]
argmin has joined #bitcoin-core-dev
jm has quit [Ping timeout: 255 seconds]
argmin has quit [Quit: argmin]
<hebasto>
laanwj: ^^ is this due `$(nproc)` which is not available on freebsd?
yanmaani has quit [Ping timeout: 240 seconds]
yanmaani has joined #bitcoin-core-dev
sipsorcery has quit [Read error: Connection reset by peer]
sipsorcery has joined #bitcoin-core-dev
Talkless has quit [Quit: Konversation terminated!]
tripleslash has quit [Ping timeout: 246 seconds]
z9z0b3t1c has joined #bitcoin-core-dev
tripleslash has joined #bitcoin-core-dev
z9z0b3t1_ has quit [Ping timeout: 255 seconds]
___nick___ has quit [Ping timeout: 260 seconds]
yanmaani has quit [Remote host closed the connection]
yanmaani has joined #bitcoin-core-dev
tripleslash has quit [Ping timeout: 255 seconds]
tripleslash has joined #bitcoin-core-dev
jarthur has joined #bitcoin-core-dev
Mousticke has joined #bitcoin-core-dev
Mousticke has quit [Quit: Client closed]
sipsorcery has quit [Ping timeout: 255 seconds]
Aaronvan_ has quit [Quit: Leaving...]
<stick>
yeah, that's it, no nproc on bsd
Guest79 has joined #bitcoin-core-dev
Guest47 has joined #bitcoin-core-dev
Guest47 has quit [Client Quit]
Guest47 has joined #bitcoin-core-dev
Guest47 has quit [Client Quit]
Guest79 has quit [Quit: Client closed]
jarthur has quit [Quit: jarthur]
brunoerg has quit [Remote host closed the connection]