Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: Sup-talk mailing list <sup-talk@rubyforge.org>
Subject: [sup-talk] fun stuff in git next
Date: Fri, 01 Jan 2010 13:48:15 -0800	[thread overview]
Message-ID: <1262382203-sup-1890@masanjin.net> (raw)

Thanks to inestimable Rich Lane, we have two particularly exciting
things happening now in git next:

1. Autosave. No more hitting '$' in thread-view-mode. (Actually hitting
'$' will now send you to the bottom of the buffer.)

2. Ruby 1.9 support. There are a few warts here and there, but it works!
You will need either Xapian or the special compiled-for-1.9 Ferret gem
that's been floating around for this.

Those of you following git master will also notice a bunch of new
features that have been merged down from next, in preparation for the
0.10 release.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


             reply	other threads:[~2010-01-01 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-01 21:48 William Morgan [this message]
2010-01-01 22:05 ` Edward Z. Yang
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=1262382203-sup-1890@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --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