From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
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: Tue, 27 Nov 2012 00:54:30 +0000 (GMT) [thread overview]
Message-ID: <292179.45651353977670193.JavaMail.weblogic@epv6ml08> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1006 bytes --]
> 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
>
>
>
>
>
>
>
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2012-11-27 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 0:54 MyungJoo Ham [this message]
2012-11-27 4:26 ` Re: [GIT PULL] extcon for Linux 3.8 Greg KH
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=292179.45651353977670193.JavaMail.weblogic@epv6ml08 \
--to=myungjoo.ham@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=khoroshilov@ispras.ru \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@gmail.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