From: Chris Abbey <jikes@cabbey.net>
To: <mauve-discuss@sources.redhat.com>
Subject: jacks mailing list archives, bugs, patches, etc
Date: Thu, 04 Nov 2004 05:04:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0411031731070.6870-100000@tweedle.cabbey.net> (raw)
Can anyone think of any good use for the mailing list archive from the
old jacks list, or the small number of bugs and the one patch that are
outstanding on the dw server?
The mailing list was shutdown today, and I have the mbox archive here if
we can think of anything usefull to do with it.
The bugs and patches will be around a bit longer, but not forever, as the
project on dw will eventually be deactivated.
The vast majority of the bugs are from Neil Gafter, there's one from me as
well that is likely a bug in the upstream tcltest framework.
The one patch out there is a testcase for import that needs to find a home
in the suite, if there isn't already a test of the same thing and if the
test even seems legit to folks.
--
Never make a technical decision based upon the politics of the situation.
Never make a political decision based upon technical issues.
The only place these realms meet is in the mind of the unenlightened.
-- Geoffrey James, The Zen of Programming
reply other threads:[~2004-11-04 5:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.33.0411031731070.6870-100000@tweedle.cabbey.net \
--to=jikes@cabbey.net \
--cc=mauve-discuss@sources.redhat.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).