Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Ali Lown <ali@lown.me.uk>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] state of maildir-sync branch?
Date: Mon, 15 Nov 2010 15:52:59 -0500	[thread overview]
Message-ID: <1289854240-sup-7909@zyrg.net> (raw)
In-Reply-To: <1289849196-sup-128@alipc-laptop>

Excerpts from Ali Lown's message of Mon Nov 15 14:29:22 -0500 2010:
> What happened to this branch, because it hasn't been worked on since July, but doesn't appear to have been merged into master/next.
> Does anyone know what else needs to be done to get it suitable for merging (besides a git rebase)?
> -Ali

I'll take a look.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2010-11-15 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 19:29 Ali Lown
2010-11-15 20:52 ` Rich Lane [this message]
2010-11-16 14:30 ` Damien Leone
2010-11-16 15:35   ` Alvaro Herrera
2010-11-18 12:30     ` Damien Leone
2010-11-18 14:50       ` Alvaro Herrera

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=1289854240-sup-7909@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=ali@lown.me.uk \
    --cc=sup-devel@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