From: Robert Yang <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/1 RFC] fetch2/git.py: fix the filename too long error
Date: Sat, 9 Nov 2013 00:31:50 +0800 [thread overview]
Message-ID: <cover.1383927399.git.liezhi.yang@windriver.com> (raw)
The following changes since commit d6cc7c8ed76c8b1117cf03c7bd4b0742f98f79b3:
toolchain-scripts/meta-environment: Further cleanup code duplication (2013-11-06 11:02:27 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib rbt/toolong
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=rbt/toolong
Robert Yang (1):
fetch2/git.py: fix the filename too long error
bitbake/lib/bb/fetch2/git.py | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2013-11-08 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 16:31 Robert Yang [this message]
2013-11-08 16:31 ` [PATCH 1/1 RFC] fetch2/git.py: fix the filename too long error Robert Yang
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=cover.1383927399.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bitbake-devel@lists.openembedded.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