From: Jerry DeLisle <jvdelisle@verizon.net>
To: gfortran <fortran@gcc.gnu.org>
Cc: gcc patches <gcc-patches@gcc.gnu.org>
Subject: Trunk merged into fortran-dev branch
Date: Fri, 26 Feb 2010 23:39:00 -0000 [thread overview]
Message-ID: <4B883E0E.9090805@verizon.net> (raw)
I have successfully merged trunk into fortran-dev.
Transmitting file data
...
Committed revision 157099.
Regards,
Jerry
next reply other threads:[~2010-02-26 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 23:39 Jerry DeLisle [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-27 5:48 Jerry DeLisle
2010-09-27 6:17 ` Basile Starynkevitch
2010-09-27 9:31 ` Jerry DeLisle
2010-03-21 7:21 Jerry DeLisle
2010-01-09 22:02 Jerry DeLisle
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=4B883E0E.9090805@verizon.net \
--to=jvdelisle@verizon.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.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).