On 02/02/2021 07:20, Martin Blais wrote: > Hi, > > Part of v3 plans is thinning out the repository. > I've just moved the beancount.ingest directory from beancount to a new > repository. > Announcing: > https://github.com/beancount/beangulp
When beangulp was split off from the beancount repository, the git history was not preserved. Among other things, this made it not easy to identify contributors to the code. To address this, I used git-filter-repo to carve beangulp out of beancount preserving history. I just foce pushed the result to the beangulp master branch. The contents of the repository are identical, but the most recent git commits have been rebased and thus have different commit IDs. If anyone has open pull request or local commits, these will need to be rebased on top of the new repository head. "git rebase --help" has instructions on how to do it in the "RECOVERING FROM UPSTREAM REBASE" section. Let me know if you need help with it. I think I started this work when most likely I was the only one beangulp changes pending merge (Github reported that there were only an handful of forks of the beangulp repo and none had any commit to it). Unfortunately, by the time I pushed the new history a PR for beangulp popped up. I hope it is not too much trouble to rebase it. Sorry for the disruption, but I feel that preserving the history was worth the inconvenience. Cheers, Dan -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/7ee5273f-9857-6d83-9f0a-f667ac34c16d%40grinta.net.
