I've quickly archived all the Beancount issues and the repo in prevision of
the Mercurial shutdown next week.
New changes will be lost.
It's possible to reimport them into another Mercurial project I think,
that's the easiest avenue.
I still need to figure out where this is all going to go.
As you
Hi Martin,
if you need help, please let us know.
If you want to keep it simple:
a) just archive the Mercurial stuff
b) import the latest version only to Github
If you have the issues in a readable format ask us, your followers, to
import them. I am sure some of us have plenty of time now. :-(
I do not know about importing archived Issues but a Fossil Repository
contains the issues alongside everything else (wiki,
issues/bugtracker,...). Maybe merging and hosting a Fossil repository might
be a solution?
On Sunday, March 22, 2020 at 3:21:43 PM UTC, Martin Blais wrote:
>
> I've quickly
* Uwe Ziegenhagen [2020-03-22 16:26]:
> If you have the issues in a readable format ask us, your followers, to
> import them. I am sure some of us have plenty of time now. :-(
https://github.com/jeffwidman/bitbucket-issue-migration
And someone already said he created a Git repo.
--
Martin Mich
We already hvae a github repo here:
https://github.com/beancount/beancount
It's just not up-to-date because I don't use it, and sync'ing fails
regularly (and I don't have time to fix it)
On Sun, Mar 22, 2020 at 12:04 PM Martin Michlmayr wrote:
> * Uwe Ziegenhagen [2020-03-22 16:26]:
> > If you
I just attempted to update the github mirror now and it fails again.
I'm spending more time fixing this up than I have, I just can't, have to
figure out trades for tomorrow's session
I'd contemplate switching over if I knew it was possible to switch back
(demonstrated) without losing any data
On
On Sun, Mar 22, 2020 at 01:05:20PM -0400, Martin Blais wrote:
> I just attempted to update the github mirror now and it fails again.
> I'm spending more time fixing this up than I have, I just can't, have to
> figure out trades for tomorrow's session
> I'd contemplate switching over if I knew it wa
I just updated my github mirror with your latest commit:
https://github.com/xuhcc/beancount/commits/master
The tool that I'm using is git-remote-hg
(https://github.com/mnauw/git-remote-hg). It allows both pull and push
operations to remote mercurial repos, but local repo needs to be in git
form
On Sun, Mar 22, 2020 at 1:20 PM Stefano Zacchiroli wrote:
> On Sun, Mar 22, 2020 at 01:05:20PM -0400, Martin Blais wrote:
> > I just attempted to update the github mirror now and it fails again.
> > I'm spending more time fixing this up than I have, I just can't, have to
> > figure out trades for
On Sun, Mar 22, 2020 at 01:58:53PM -0400, Martin Blais wrote:
> So either I find another Hg hosting (doesn't seem to be anything foss
> friendly with issue tracking out there I feel confident about), or try
> a move to github.
It's known™ that I'd personally favor a move to a git-based hosting.
Bu
One area that is missing in fava today is investment tools.
I've found Beancount to be very well designed to capture and represent
almost anything necessary for handling investments in the realm of personal
finance (thanks, Martin!), and Fava to be a terrific front end (thanks,
Fava authors)!
Kirill: Thanks, I managed to re-export from scratch using git-remote-log.
Despite this being a completely separate export, it did manage to update
the github.com/beancount/beancount repo, so it must be using stable hashes
or some other way to avoid allocating new hashes when exporting (which is
gre
On Sun, Mar 22, 2020 at 8:48 PM Martin Blais wrote:
> Kirill: Thanks, I managed to re-export from scratch using git-remote-log.
> Despite this being a completely separate export, it did manage to update
> the github.com/beancount/beancount repo, so it must be using stable
> hashes or some other w
I've added some comments here:
https://github.com/beancount/fava/issues/1082#issuecomment-602310904
Let us know if you want to continue the conversation here, on fava or on
fava-investor!
Dave
--
You received this message because you are subscribed to the Google Groups
"Beancount" group.
To
14 matches
Mail list logo
