unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: Aaron Suggs <aaron@ktheory.com>
Subject: Re: Address already in use
Date: Mon, 25 Jun 2012 18:10:58 +0000	[thread overview]
Message-ID: <20120625181058.GA25487@dcvr.yhbt.net> (raw)
In-Reply-To: <0C6B40126128400FB2DD3A620F4CDB21@gmail.com>

Aaron Suggs <aaron@ktheory.com> wrote:
> P.S. I've tried to contribute the patch upstream via this list, but it
> keeps getting rejected for having the wrong content type. Then I gave
> up. I'm fine chalking it up to my own stupidity/laziness…just wanted
> to put it out there that contributing could be easier. :-)

I want it to be easy, too, but that includes being easy for me to
review.  Inline patches are easiest as I can quote relevant portions
of the email in the reply.

Did you try "git send-email"?  It helps you format messages correctly
if your MUA isn't capable of that.

Otherwise, yes, you can upload the commit to any public git repository
and I can clone + run "git show" / "git log -p" to see your changes and
reply to them inline.  It takes me longer and I'll end up faking the
quoted portions (via git format-patch --stdout ... | sed -e 's/^/> '
when reviewing.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2012-06-25 18:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 13:02 Address already in use Manuel Palenciano Guerrero
2012-06-25 13:41 ` Jérémy Lecour
2012-06-25 13:42 ` Aaron Suggs
2012-06-25 18:10   ` Eric Wong [this message]
2012-06-25 21:10   ` Eric Wong
2012-06-25 20:28 ` Eric Wong
2012-06-25 21:03   ` Manuel Palenciano Guerrero
2012-06-25 23:57     ` Eric Wong

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

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120625181058.GA25487@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=aaron@ktheory.com \
    --cc=mongrel-unicorn@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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).