From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alex Elder <aelder@sgi.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS (2 regression fixes)
Date: Fri, 30 Oct 2009 12:48:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0910301247480.31845@localhost.localdomain> (raw)
In-Reply-To: <200910301857.n9UIvZ6w009983@stout.americas.sgi.com>
On Fri, 30 Oct 2009, Alex Elder wrote:
>
> Linus, Christoph Hellwig sent a pull request for these patches from
> the xfs-dev tree on kernel.org earlier today. (Pointing this out to
> hopefully avoid confusion.)
I'll pull from Christophs tree directly - I refuse to pull from trees that
have more merge commits than actual real commits.
Linus
> Alex Elder (2):
> Merge branch 'master' of ssh://oss.sgi.com/oss/git/xfs/xfs into for-linus
> Merge branch 'master' of git://git.kernel.org/.../torvalds/linux-2.6 into for-linus
Both of these seem pointless, and a sign of something wrong.
Linus
prev parent reply other threads:[~2009-10-30 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 18:57 Alex Elder
2009-10-30 19:48 ` Linus Torvalds [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=alpine.LFD.2.01.0910301247480.31845@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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
all inboxes | Powered by JetHome®