netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: padovan@profusion.mobi
Cc: gustavo@padovan.org, johan.hedberg@gmail.com,
	linville@tuxdriver.com, marcel@holtmann.org,
	netdev@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2012-03-01
Date: Sat, 03 Mar 2012 14:46:00 -0500 (EST)	[thread overview]
Message-ID: <20120303.144600.2037752804675250467.davem@davemloft.net> (raw)
In-Reply-To: <20120303164655.GA5275@joana>

From: Gustavo Padovan <padovan@profusion.mobi>
Date: Sat, 3 Mar 2012 13:46:55 -0300

> This is something we can't do.

Then I cannot pull from you.

I gave you guys a one-off free pass last time around when I took
you stuff in via John's last wireless pull request.

That was your opportunity to start doing things correct yet not
be inconveniences that one time.

But if I just keep pulling from you, that sends absolutely the
message.  I am serious and you must start making your code fit
my requirements for suitability.

  reply	other threads:[~2012-03-03 19:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  2:55 pull request: bluetooth-next 2012-03-01 Gustavo Padovan
2012-03-02  3:16 ` David Miller
2012-03-02  3:23   ` David Miller
2012-03-02  3:26     ` David Miller
2012-03-02  4:13       ` Joe Perches
2012-03-02  5:35         ` [PATCH] checkpatch: Add --strict tests for braces, comments and casts Joe Perches
2012-03-02  5:54           ` [PATCH] checkpatch: Add --strict test for strings split across multiple lines Joe Perches
2012-03-02 16:37       ` pull request: bluetooth-next 2012-03-01 Gustavo Padovan
2012-03-02 21:15         ` David Miller
2012-03-03 16:46           ` Gustavo Padovan
2012-03-03 19:46             ` David Miller [this message]
2012-03-03 19:47             ` David Miller
2012-03-03 20:04               ` Joe Perches
2012-03-03 20:06                 ` David Miller

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=20120303.144600.2037752804675250467.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linville@tuxdriver.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=padovan@profusion.mobi \
    /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).