Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] updated edge branch
Date: Mon, 22 Feb 2010 07:48:30 +0200	[thread overview]
Message-ID: <1266817465-sup-993@tilus.net> (raw)
In-Reply-To: <1266797479-sup-3532@zyrg.net>

Rich Lane, 2010-02-22 02:20:
> There are a bunch of patches that haven't been merged to mainline
> yet, so I merged them to my edge branch.

Thanks.  Now I don't have to (re)integrate them to my daily sup all
the time.

> I didn't look too hard at them so don't assume that this branch
> could be merged to mainline as-is.

Was hookifying missing attachment detector intentionally left out?
http://github.com/terotil/sup/commit/ae317d351b9b1e4210d472cfe43b8e60cd4257c4

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


      reply	other threads:[~2010-02-22  5:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22  0:20 Rich Lane
2010-02-22  5:48 ` Tero Tilus [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=1266817465-sup-993@tilus.net \
    --to=tero@tilus.net \
    --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