From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
Subject: [sup-talk] "X-" headers
Date: Fri, 31 Oct 2008 12:56:04 -0400 [thread overview]
Message-ID: <1225472018-sup-3924@cabinet> (raw)
In-Reply-To: <1225159970-sup-8568@entry>
Excerpts from William Morgan's message of Mon Oct 27 22:15:23 -0400 2008:
> No, that's fine. Posting patches here is fine too, but no one really
> reads them except for me, so... whatever's easiest for you. Official
> Gitorious merge requests also work.
I've been known to read patches posted here in the past, and even apply
them locally if it was something I really wanted and I didn't want to
wait for it to make it to next.
I don't think I'm alone, although there probably aren't many of us.
Just, y'know, to debate the irrelevant point.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20081031/c6a80f5b/attachment-0001.bin>
prev parent reply other threads:[~2008-10-31 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 18:41 Decklin Foster
2008-10-28 2:15 ` William Morgan
2008-10-31 16:56 ` Marc Hartstein [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=1225472018-sup-3924@cabinet \
--to=marc.hartstein@alum.vassar.edu \
/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