From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>,
virtualization@lists.osdl.org,
Network Development <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Asias He <asias@redhat.com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Subject: Re: [PULLv2] vhost: cleanups and fixes
Date: Thu, 2 May 2013 13:26:41 -0700 [thread overview]
Message-ID: <CA+55aFyzq+EBHiKYyEw3OXWKeeTbwt1sCYACfD4YsOWCBBZTVQ@mail.gmail.com> (raw)
In-Reply-To: <20130502201106.GA17385@redhat.com>
On Thu, May 2, 2013 at 1:11 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> Hi Linus,
> This is exactly same code as my previous pull sent earlier, the diffstat
> was wrong however, I did a merge with master which fixed that.
See my other email. THIS IS NOT A VALID REASON TO DO A BACK-MERGE!
Extraneous merge commits that have no actual reason for development
are bad. They make it much harder to see what the actual development
thread was, because they mix up different branches. In fact, the whole
problem with the diffstat started with *another* extraneous merge, so
the "fix" was a result of a previous merge. This is exactly the kind
of reason why we want merges to be done by upstream developers, not
"back-merges" by downstream.
Now that merge is in your development tree, and if/when you start
doing development on top of that, the same kind of problem will
continue. Together with making it much harder to see in the history
what _your_ development stream was, because now it's no longer linear
and mixes in random points of the merge window.
Don't do this. Why do I have to write one of these "DON'T DO
BACK-MERGES" every single merge window? I really wish people listened,
instead of every single developer deciding that "it's ok if _I_ do it,
I'm sure Linus is complaining about all those *other* morons out
there".
When I say "don't do back-merges", I mean *you*. Yes, you. Not
somebody else. You.
Linus
next prev parent reply other threads:[~2013-05-02 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 20:11 [PULLv2] vhost: cleanups and fixes Michael S. Tsirkin
2013-05-02 20:26 ` Linus Torvalds [this message]
2013-05-02 20:32 ` Linus Torvalds
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=CA+55aFyzq+EBHiKYyEw3OXWKeeTbwt1sCYACfD4YsOWCBBZTVQ@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=asias@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.osdl.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).