Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Tero Tilus <tero@tilus.net>
Cc: Sup developers <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Publish hook
Date: Sat, 27 Feb 2010 03:26:27 -0500	[thread overview]
Message-ID: <1267259141-sup-1539@zyrg.net> (raw)
In-Reply-To: <1266783512-sup-8493@tilus.net>

Branch publish-hook, merged to next.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


      reply	other threads:[~2010-02-27  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21 20:24 Tero Tilus
2010-02-27  8:26 ` Rich Lane [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=1267259141-sup-1539@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=sup-devel@rubyforge.org \
    --cc=tero@tilus.net \
    /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