From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: git@vger.kernel.org
Subject: Re: Feature request - Subtree checkouts
Date: Tue, 10 Apr 2007 09:20:11 -0400 [thread overview]
Message-ID: <20070410132011.GH5436@spearce.org> (raw)
In-Reply-To: <20070410074444.GA18541@curie-int.orbis-terrarum.net>
"Robin H. Johnson" <robbat2@gentoo.org> wrote:
> P.S. Does this list do some weird spam-blocking? I've tried 3 times now
> to use git-send-email to send an unrelated minor patch set
> (--subject-prefix for git-format-patch), and it has never shown up on
> the list :-(.
Yes. It has cut down on our spam, but it has also caused some
things to be blocked, almost without good reason. ;-)
I send a fair number of patches to this list (at times anyway) and
am also unable to use git-send-email. If I have the email also CC
back to me it does make it through a number of SMTP server hops,
including my own spam filters, but it never makes it through the
Git mailing list. So I dump the patches to an mbox with --stdout,
open them up in mutt and resend them there. I've bound shift-G
to resend-message for that purpose...
--
Shawn.
next prev parent reply other threads:[~2007-04-10 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 7:44 Feature request - Subtree checkouts Robin H. Johnson
2007-04-10 13:20 ` Shawn O. Pearce [this message]
2007-04-10 20:28 ` Junio C Hamano
[not found] ` <Pine.LNX.4.64.0704101338060.6730@ woody.linux-foundation.org>
2007-04-10 20:56 ` Linus Torvalds
2007-04-10 21:33 ` [OT] " alan
2007-04-10 22:12 ` Linus Torvalds
2007-04-10 22:30 ` alan
2007-04-10 22:49 ` Christer Weinigel
2007-04-10 23:20 ` alan
2007-04-10 22:56 ` David Lang
2007-04-12 9:55 ` Jimmy Tang
2007-04-10 21:10 ` Robin H. Johnson
2007-04-10 22:04 ` Robin H. Johnson
2007-04-10 23:41 ` Shawn O. Pearce
2007-04-14 8:59 ` Johannes Schindelin
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=20070410132011.GH5436@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=robbat2@gentoo.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;
as well as URLs for NNTP newsgroup(s).