From: "Felipe Balbi" <felipebalbi@users.sourceforge.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Andreas Ericsson" <ae@op5.se>,
git@vger.kernel.org, "Felipe Balbi" <felipe.lima@indt.org.br>
Subject: Re: [PATCH 1/1] git-send-email: Add a --suppress-all option
Date: Tue, 18 Sep 2007 09:29:02 -0400 [thread overview]
Message-ID: <31e679430709180629p328abba8ud4c4ce7fef7645e4@mail.gmail.com> (raw)
In-Reply-To: <20070918132251.GB12120@fieldses.org>
Hi,
On 9/18/07, J. Bruce Fields <bfields@fieldses.org> wrote:
> On Tue, Sep 18, 2007 at 09:40:55AM +0200, Andreas Ericsson wrote:
> > Felipe Balbi wrote:
> >> From: Felipe Balbi <felipe.lima@indt.org.br>
> >> This patch adds a --suppress-all option to avoid sending emails
> >> to everybody but the ones listed by --to option.
> >
> > To my minds eye, --suppress-all is equivalent to --dry-run. Could you
> > rename it to "--cc-nobody" or some such?
> >
> > On a side-note, I've never really understood why git-send-email *by
> > default*
> > sends to a bazillion people. Does anybody ever use it without suppressing
> > most of the CC targets?
>
> Yes. I never suppress the cc's. The cc-everyone thing is standard on
> the kernel mailing lists.
>
> The one exception is if I'm just sending the series to myself as a test.
And that the motivation for this patch :-p
Internally (in my company, where I work), we send patches to each
other for code review before sending it publicly.
>
> --b.
>
--
Best Regards,
Felipe Balbi
felipebalbi@users.sourceforge.net
next prev parent reply other threads:[~2007-09-18 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 18:33 [PATCH 1/1] git-send-email: Add a --suppress-all option Felipe Balbi
2007-09-18 7:40 ` Andreas Ericsson
2007-09-18 13:22 ` J. Bruce Fields
2007-09-18 13:29 ` Felipe Balbi [this message]
2007-09-18 14:15 ` David Kastrup
2007-09-18 14:39 ` Felipe Balbi
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31e679430709180629p328abba8ud4c4ce7fef7645e4@mail.gmail.com \
--to=felipebalbi@users.sourceforge.net \
--cc=ae@op5.se \
--cc=bfields@fieldses.org \
--cc=felipe.lima@indt.org.br \
--cc=git@vger.kernel.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://80x24.org/mirrors/git.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).