From: Tom Tromey <tromey@redhat.com>
To: gnustuff@thisiscool.com
Cc: java-patches@gcc.gnu.org, mauve-discuss@sources.redhat.com
Subject: Re: PATCH for Date.parse
Date: Sun, 04 Jan 2004 20:45:00 -0000 [thread overview]
Message-ID: <874qvb4fic.fsf@fleche.redhat.com> (raw)
In-Reply-To: <C9YT5Z08RMFNHDTP2YJFNJ71S755Y.3ff77b60@p733>
>>>>> "Mohan" == Mohan Embar <gnustuff@thisiscool.com> writes:
Mohan> Tom had once mentioned that Mauve checkins were
Mohan> a free-for-all, but I've only be able to get at
Mohan> the sources via anonymous CVS. How do I check
Mohan> stuff into Mauve?
I've added you to the Mauve group on sources.redhat.com.
Tom
prev parent reply other threads:[~2004-01-04 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FF761D7.8050200@bothner.com>
2004-01-04 2:33 ` Mohan Embar
2004-01-04 2:53 ` Per Bothner
2004-01-04 20:45 ` Tom Tromey [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=874qvb4fic.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gnustuff@thisiscool.com \
--cc=java-patches@gcc.gnu.org \
--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).