From: Gary Benson <gbenson@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: Re: rhug checklinkages
Date: Fri, 07 Feb 2003 10:14:00 -0000 [thread overview]
Message-ID: <20030207101354.GA27638@redhat.com> (raw)
In-Reply-To: <1044603304.1600.45.camel@escape>
Anthony Green wrote:
> On Thu, 2003-02-06 at 10:05, Gary Benson wrote:
> > Output attached for those without a new enough Python. I'm going
> > to correct the packages that I've been working on but I'll not
> > touch the rest -- I don't want to trash them for anyone ;)
>
> This looks interesting. Did you post the script? I can't find it
> for some reason.
It's in the root of the RHUG CVS tree, called checklinkages. Or get it here:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/rhug/checklinkages?rev=1.1&content-type=text/plain&cvsroot=rhug
Cheers,
Gary
[ gbenson@redhat.com ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]
next prev parent reply other threads:[~2003-02-07 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030206180141.14899.qmail@sources.redhat.com>
2003-02-06 18:05 ` Gary Benson
2003-02-07 7:32 ` Anthony Green
2003-02-07 10:14 ` Gary Benson [this message]
2003-02-07 10:31 ` Xerces linkages Gary Benson
2003-02-07 15:42 ` Anthony Green
2003-02-07 17:14 ` Gary Benson
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=20030207101354.GA27638@redhat.com \
--to=gbenson@redhat.com \
--cc=rhug-rhats@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).