From: Nicholas Henke <roughneck@gentoo.org>
To: Mark Farver <mfarver@mindbent.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gnucash 1.8 test ebuild
Date: Mon, 10 Feb 2003 18:57:29 -0500 [thread overview]
Message-ID: <20030210185729.3d76dbfd.roughneck@gentoo.org> (raw)
In-Reply-To: <20030210234025.GA27727@mindbent.org>
On Mon, 10 Feb 2003 17:40:25 -0600
Mark Farver <mfarver@mindbent.org> wrote:
> Impatient for a 1.8 ebuild of gnucash I tried to update it myself...
> it works for me, but it might not for you. If anyone with CVS access
> wants to clean it up and submit it feel free.
>
> http://www.mindbent.org/download/gnucash-1.8.0.ebuild
>
> Might want to wait until 1.8.1 comes out "tonight" since the gnucash
> folks say 1.8.1 fixes several showstopper bugs (including qif file
> importing).
>
>
> Mark
BTW -- I have been using 1.8.0 for the entire weekend ( put 3 months of
my books into it), and I would call it stable on ppc.
Nic
--
Nicholas Henke
Linux Cluster Systems Programmer
Liniac Project - Univ. of Pennsylvania
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-02-11 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 23:40 [gentoo-dev] Gnucash 1.8 test ebuild Mark Farver
2003-02-10 23:57 ` Nicholas Henke [this message]
2003-02-11 0:14 ` Mark Farver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030210185729.3d76dbfd.roughneck@gentoo.org \
--to=roughneck@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=mfarver@mindbent.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox