On 2026-03-27, Tavis Ormandy wrote:
> On 2026-03-27, John Wiegley wrote:
>> Hi Tavis,
>>
>> Since I had spare tokens that were about to expire out last night, I decided
>> to set Claude on fixing every remaining issue in GitHub with a “bug” label.
>> The result -- so far -- is 89 PRs (and counting) waiting for review.
>>
>> I was wondering if you’d like to check out any of these that might affect
>> areas you’re interested in:
>>
>> https://github.com/ledger/ledger/pulls?page=1&q=is%3Apr+is%3Aopen
>>
>> Once this set goes in, we’re going to be getting very close to “inbox zero”
>> on
>> our GitHub issues, with just feature requests remaining.
>>
>
> I can test -- no problem at all! Can you keep the new changes in a
> branch temporarily?
>
> I see there's a lot of changes, I just think that will make it easier to
> compare this new batch to main.
>
I'm not really a git expert, but I tried something like...
for branch in $(git branch -a | grep 'johnw/fix-'); do
git merge --abort
git reset --hard main
git clean -fd -e build/ -e check.sh
if git merge "$branch" --no-edit; then
cmake ...
if diff -u <(build/ledger bal) <(ledger bal); then
...
fi
fi
done
There are a lot of breaking changes, it might take some time to minimize
testcases. What is the best way to handle it?
Tavis.
--
_o) $ lynx lock.cmpxchg8b.com
/\\ _o) _o) $ finger [email protected]
_\_V _( ) _( ) @taviso
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/ledger-cli/10q8ujj%24icc%241%40ciao.gmane.io.
