From: Roland Dreier <rolandd@cisco.com>
To: Greg KH <greg@kroah.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 06:44:55 -0700 [thread overview]
Message-ID: <52zmpxmhm0.fsf@cisco.com> (raw)
In-Reply-To: <20050928093633.GA12757@kroah.com> (Greg KH's message of "Wed, 28 Sep 2005 02:36:33 -0700")
Greg> I didn't think that git pulls were going to be allowed from
Greg> subsystem maintainers after -rc1 came out. After that,
Greg> patches by email were required to be sent, not git pulls.
Greg> This does cause a bit more work for the maintainer, but it
Greg> ensures that they only send the patches they really want to
Greg> get in.
I specifically asked Linus about this a couple of weeks ago, and he
said that bug-fix-only git merges are file. See http://lkml.org/lkml/2005/9/13/277
- R.
next prev parent reply other threads:[~2005-09-28 13:45 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
2005-09-28 10:58 ` Anton Altaparmakov
2005-09-28 13:44 ` Roland Dreier [this message]
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=52zmpxmhm0.fsf@cisco.com \
--to=rolandd@cisco.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--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