From: David Miller <davem@davemloft.net>
To: corcodel.marian@gmail.com
Cc: netdev@vger.kernel.org, asu@192-168-0-3.rdsnet.ro
Subject: Re: [PATCH net-next]r8169:Disable advertise full duplex on chip id RTL_GIGA_MAC_VER_09. Disable advertise full duplex on chip id RTL_GIGA_MAC_VER_09 wich support random full duplex.(very sad) On branch master Your branch is ahead of 'origin/master' by 18 commits. (use "git push" to publish your local commits)
Date: Sat, 18 Jul 2015 22:21:14 -0700 (PDT) [thread overview]
Message-ID: <20150718.222114.714819532825166156.davem@davemloft.net> (raw)
In-Reply-To: <1437213838-29318-1-git-send-email-corcodel.marian@gmail.com>
This is still ver far from acceptable. You aren't even talking to us when
we ask you questions and ask you to make changes, you just make another
improperly formatted submission of a bad patch all over again.
Your entire description is in your Subject line, and it insufficiently
describes your change.
Frankly, I am very sick and tired of these low quality submissions. I want to
know where these changes are coming from, who they are important to, and most
importantly why it is so difficult for you to submit your changes properly.
Just simply _LOOK_ at postings by other developers who submit changes
that successfully get accepted by us.
_LOOK_ at how their Subject line looks, and mimick what they do _EXACTLY_
_LOOK_ at how their commit messages look, how detailed they are, how
descriptive they are, and how they are formatted and composed, and
mimick _EACTLY_ what they are doing.
This isn't rocket science, if you want us to take your changes seriously
you _MUST_ learn how to conform to our patch submission methods and
expectations.
Thanks.
prev parent reply other threads:[~2015-07-19 5:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 10:03 [PATCH net-next]r8169:Disable advertise full duplex on chip id RTL_GIGA_MAC_VER_09. Disable advertise full duplex on chip id RTL_GIGA_MAC_VER_09 wich support random full duplex.(very sad) On branch master Your branch is ahead of 'origin/master' by 18 commits. (use "git push" to publish your local commits) Corcodel Marian
2015-07-19 5:21 ` David Miller [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=20150718.222114.714819532825166156.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=asu@192-168-0-3.rdsnet.ro \
--cc=corcodel.marian@gmail.com \
--cc=netdev@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.
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).