[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <292179.45651353977670193.JavaMail.weblogic@epv6ml08>
Date: Tue, 27 Nov 2012 00:54:30 +0000 (GMT)
From: MyungJoo Ham <myungjoo.ham@...sung.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"myungjoo.ham@...il.com" <myungjoo.ham@...il.com>,
ÃÖÂù¿ì <cw00.choi@...sung.com>,
¹Ú°æ¹Î <kyungmin.park@...sung.com>,
"sachin.kamat@...aro.org" <sachin.kamat@...aro.org>,
"khoroshilov@...ras.ru" <khoroshilov@...ras.ru>
Subject: Re: Re: [GIT PULL] extcon for Linux 3.8
> 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)
Cheers,
MyungJoo
>
> thanks,
>
> greg k-h
>
>
>
>
>
>
>
Powered by blists - more mailing lists