From: Yu Ke <ke.yu@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Richard Purdie <richard.purdie@intel.com>, poky@yoctoproject.org
Subject: Re: [PATCH 0/4] fetcher2 git cleanup
Date: Sat, 28 May 2011 09:40:45 +0800 [thread overview]
Message-ID: <4DE0529D.3010504@intel.com> (raw)
In-Reply-To: <BANLkTinAp6G=xhwmvfagDv2QdhzCo04Akw@mail.gmail.com>
on 2011-5-28 1:12, Khem Raj wrote:
> On Fri, May 27, 2011 at 1:53 AM, Yu Ke<ke.yu@intel.com> wrote:
>> This patch series is some clean up of the git fetcher according to the comment
>> from mailing list.
>>
>> The following changes since commit 9bccbc5fbc71b331911b558a2ba15e0a6d0046b4:
>> Nitin A Kamble (1):
>> tcmode-default: workaround for gcc 4.6.0 failure on beagleboard
>>
>> are available in the git repository at:
>>
>> git://git.pokylinux.org/poky-contrib kyu3/git-cleanup
>> http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/log/?h=kyu3/git-cleanup
>>
>> Yu Ke (4):
>> fetche2 git: change default protocol from rsync to git
>> fetcher2 git: unify the nocheckout option format
>
> above patch has typo in commit message nocheckou is missing 't'
>
>> fetcher2/git: add document for git fetcher supported options
>
> while the contents are ok there are grammatical corrections needed in the above
It is good reminder. Thank Khem and Richard. I will take care of it next
time.
Regards
Ke
next prev parent reply other threads:[~2011-05-28 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 8:53 [PATCH 0/4] fetcher2 git cleanup Yu Ke
2011-05-27 8:53 ` [PATCH 1/4] fetche2 git: change default protocol from rsync to git Yu Ke
2011-05-27 8:53 ` [PATCH 2/4] fetcher2 git: unify the nocheckout option format Yu Ke
2011-05-27 8:53 ` [PATCH 3/4] fetcher2/git: add document for git fetcher supported options Yu Ke
2011-05-27 8:53 ` [PATCH 4/4] fetch2 git: enhance the unpack by using "git checkout" Yu Ke
2011-05-27 17:12 ` [PATCH 0/4] fetcher2 git cleanup Khem Raj
2011-05-28 1:40 ` Yu Ke [this message]
2011-05-27 17:12 ` Richard Purdie
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=4DE0529D.3010504@intel.com \
--to=ke.yu@intel.com \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.