From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: xconq7 <xconq7@sources.redhat.com>
Subject: Re: New Source Tarball and Windows Installer
Date: Sun, 26 Sep 2004 16:01:00 -0000 [thread overview]
Message-ID: <4156DF31.9060000@phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0409260930210.18957-100000@diamond.ansuz.sooke.bc.ca>
mskala@ansuz.sooke.bc.ca wrote:
> On Sun, 26 Sep 2004, Eric McDonald wrote:
>
>> I have released a new installer for Windows and new source tarball.
>>They can be gotten at:
>> http://xconq_hacker.home.comcast.net
>
> Will you be checking these into CVS? Is CVS still a good way to stay
> up to date at all? I get the impression a lot of recent work (not
> just yours) hasn't been going in there.
This is a bit of a tricky issue. If all was well and good, then I would
have been checking in regularly during the past month. However, due to
an incident that occurred last month (and several minor ones before
then), I feel that I cannot guarantee the integrity of what I commit to
the CVS repository on 'sources.redhat.com'. This has led me to maintain
my own personal CVS repository. I know that this may be inconvenient to
some, and I'm sorry for the inconvenience. I hope that the situation can
be resolved on good terms in the near future, which is why I continue to
associate with the Xconq project. If not, then I suppose you will have
the option of checking my alternative sources (under a different
"banner") out of a public CVS repository somewhere else, sometime in the
future....
As for others not checking in things, there are only a few others who
have CVS write access, and of them, only Jim has shown vital signs in
the past month. I am not aware of anyone else, who has CVS write access,
maintaining a separate branch to the sources.
Eric
prev parent reply other threads:[~2004-09-26 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 13:35 Eric McDonald
2004-09-26 14:02 ` mskala
2004-09-26 16:01 ` Eric McDonald [this message]
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=4156DF31.9060000@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=mskala@ansuz.sooke.bc.ca \
--cc=xconq7@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).