From: Greg KH <greg@kroah.com>
To: Roland Dreier <rolandd@cisco.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [git pull] InfiniBand fixes for 2.6.14
Date: Wed, 28 Sep 2005 02:36:33 -0700 [thread overview]
Message-ID: <20050928093633.GA12757@kroah.com> (raw)
In-Reply-To: <524q85on6e.fsf@cisco.com>
On Tue, Sep 27, 2005 at 09:01:45PM -0700, Roland Dreier wrote:
> Linus, please pull from
>
> master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
Hm, I complained about this last time, with no response...
I didn't think that git pulls were going to be allowed from subsystem
maintainers after -rc1 came out. After that, patches by email were
required to be sent, not git pulls. This does cause a bit more work
for the maintainer, but it ensures that they only send the patches they
really want to get in.
At least that was what I thought we decided on at the kernel summit...
thanks,
greg k-h
next prev parent reply other threads:[~2005-09-28 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 4:01 [git pull] InfiniBand fixes for 2.6.14 Roland Dreier
2005-09-28 9:36 ` Greg KH [this message]
2005-09-28 10:58 ` Anton Altaparmakov
2005-09-28 13:44 ` Roland Dreier
2005-09-29 16:12 ` Greg KH
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=20050928093633.GA12757@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rolandd@cisco.com \
--cc=torvalds@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