From: Greg KH <gregkh@linuxfoundation.org>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"myungjoo.ham@gmail.com" <myungjoo.ham@gmail.com>,
최찬우 <cw00.choi@samsung.com>, 박경민 <kyungmin.park@samsung.com>,
"sachin.kamat@linaro.org" <sachin.kamat@linaro.org>,
"khoroshilov@ispras.ru" <khoroshilov@ispras.ru>
Subject: Re: Re: [GIT PULL] extcon for Linux 3.8
Date: Mon, 26 Nov 2012 20:26:31 -0800 [thread overview]
Message-ID: <20121127042631.GA17479@kroah.com> (raw)
In-Reply-To: <292179.45651353977670193.JavaMail.weblogic@epv6ml08>
On Tue, Nov 27, 2012 at 12:54:30AM +0000, MyungJoo Ham wrote:
> > On Thu, Nov 22, 2012 at 01:51:10PM +0900, MyungJoo Ham wrote:
> > > Please pull extcon patches for Linux 3.8.
> >
> > This is not a signed-tag pull request, which I thought I asked for
> > previously.
> >
> > Please create that, so that I can properly know I am getting the right
> > pull request and patches.
>
> A singed tag, "pull_req_20121122", has been already attached at the HEAD
> of for-next branch.
>
> Would it be more readable if the request is made with
> git://git.kernel.org/pub/scm/linux/kernel/git/mzx/extcon.git tags/pull_req_20121122
> rather than
> git://git.kernel.org/pub/scm/linux/kernel/git/mzx/extcon.git for-next
> ? (both point to the same commit and I tried the first URL for git request-pull; however git request-pull gives me the second URL as the result)
git request-pull should show you the proper tag, if you are using a new
version of git (i.e. something fairly recent.) What version of git are
you using? How did you create the signed tag?
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-27 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 0:54 Re: [GIT PULL] extcon for Linux 3.8 MyungJoo Ham
2012-11-27 4:26 ` Greg KH [this message]
2012-11-27 7:21 ` MyungJoo Ham
2012-11-27 14:47 ` 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=20121127042631.GA17479@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cw00.choi@samsung.com \
--cc=khoroshilov@ispras.ru \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=sachin.kamat@linaro.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