From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: Email CVS changes to gnats-commit manually
Date: Tue, 15 Jun 2004 07:30:00 -0000 [thread overview]
Message-ID: <20040614171611.GJ3528@wookimus.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 619 bytes --]
Well, it looks like I don't have access to configure the CVS repository
just yet, so I won't be able to reinstate the cvs commit emails we used
to receive via gnats-commit and gnats-diffs. I've sent email to the GNU
systems administrator for help.
Until we get that reinstated, it would probably be a good idea for
people to send email to gnats-commit manually with their updates. You
should expect a summary email from me sometime today with the changes I
recently made.
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
reply other threads:[~2004-06-14 17:16 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=20040614171611.GJ3528@wookimus.net \
--to=chewie@wookimus.net \
--cc=help-gnats@gnu.org \
/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).