From: "Frank Ch. Eigler" <fche@redhat.com>
To: Per Bothner <per@bothner.com>
Cc: overseers@sourceware.org
Subject: Re: dead link on "kawa mailing list archives"
Date: Tue, 26 Jan 2016 16:22:00 -0000 [thread overview]
Message-ID: <20160126162235.GC7295@redhat.com> (raw)
In-Reply-To: <56A6440D.8090102@bothner.com>
Hi -
> The first link on https://sourceware.org/ml/kawa/ points to
> http://www.cygnus.com/~bothner/kawa.html . Ooops.
> That should point to https://sourceware.org/kawa/ or alternatively
> the actual home-page http://www.gnu.org/software/kawa
Fixed (to point to the latter).
> Kawa still uses Sourceware for the mailing list and Subversion.
> I'm starting to get more fluent with Git (which I use for my
> new project DomTerm https://github.com/PerBothner/DomTerm) so at
> some point I might move Kawa fom Svn to Git (on either Sourceware
> or Savannah.gnu.org, not GitHub),
Let us know.
- FChE
next prev parent reply other threads:[~2016-01-26 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:50 Per Bothner
2016-01-26 16:22 ` Frank Ch. Eigler [this message]
2016-01-26 22:59 ` Per Bothner
2016-01-27 14:39 ` Frank Ch. Eigler
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=20160126162235.GC7295@redhat.com \
--to=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=per@bothner.com \
/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).