From: Christopher Larson <kergoth@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [PATCH 0/3] A few fetch bugfixes
Date: Wed, 26 Aug 2015 09:37:44 -0700 [thread overview]
Message-ID: <1440607067-14461-1-git-send-email-kergoth@gmail.com> (raw)
From: Christopher Larson <chris_larson@mentor.com>
These were discovered and fixed as a part of the git shallow mirror tarball
support implementation.
Christopher Larson (3):
bb.fetch.git: remove leading '.' from gitsrcname
bb.fetch: handle checksums consistently for mirrors
bb.fetch: don't remove the clone when an update fails
lib/bb/fetch2/__init__.py | 13 ++++++++-----
lib/bb/fetch2/git.py | 5 ++++-
2 files changed, 12 insertions(+), 6 deletions(-)
--
2.2.1
next reply other threads:[~2015-08-26 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 16:37 Christopher Larson [this message]
2015-08-26 16:37 ` [PATCH 1/3] bb.fetch.git: remove leading '.' from gitsrcname Christopher Larson
2015-08-26 16:37 ` [PATCH 2/3] bb.fetch: handle checksums consistently for mirrors Christopher Larson
2015-08-26 16:37 ` [PATCH 3/3] bb.fetch: don't remove the clone when an update fails Christopher Larson
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=1440607067-14461-1-git-send-email-kergoth@gmail.com \
--to=kergoth@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=chris_larson@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox