From: Mark Wielaard <mark@klomp.org>
To: raif@swiftdsl.com.au
Cc: mauve-discuss@sourceware.org
Subject: Re: patch to improve use with Eclipse
Date: Thu, 22 Dec 2005 21:32:00 -0000 [thread overview]
Message-ID: <1135287134.7227.211.camel@localhost.localdomain> (raw)
In-Reply-To: <200512222204.46970.raif@swiftdsl.com.au>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Hi Raif,
On Thu, 2005-12-22 at 22:04 +1100, Raif S. Naffah wrote:
> finally, did you create the symbolic link to mauve-classpath keys file?
Doh...
I saw you also updated the wiki page with those instructions.
http://developer.classpath.org/mediation/ClasspathHackingWithEclipse
It works now for me. Thanks.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-22 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 13:38 Raif S. Naffah
2005-12-21 15:07 ` Mark Wielaard
2005-12-21 23:46 ` Mark Wielaard
2005-12-22 11:03 ` Raif S. Naffah
2005-12-22 21:32 ` Mark Wielaard [this message]
2005-12-23 7:46 ` Raif S. Naffah
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=1135287134.7227.211.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=mauve-discuss@sourceware.org \
--cc=raif@swiftdsl.com.au \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).