From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] fun stuff in git next
Date: Fri, 01 Jan 2010 17:05:26 -0500 [thread overview]
Message-ID: <1262383509-sup-2516@ezyang> (raw)
In-Reply-To: <1262382203-sup-1890@masanjin.net>
Excerpts from William Morgan's message of Fri Jan 01 16:48:15 -0500 2010:
> Thanks to inestimable Rich Lane, we have two particularly exciting
> things happening now in git next:
Happy news! I'll upgrade shortly.
Cheers,
Edward
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-01-01 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 21:48 William Morgan
2010-01-01 22:05 ` Edward Z. Yang [this message]
2010-01-02 4:27 ` Richard Sandilands
2010-01-02 4:36 ` Rich Lane
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=1262383509-sup-2516@ezyang \
--to=ezyang@mit.edu \
--cc=sup-talk@rubyforge.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