Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: <Mikko.Rapeli@bmw.de>
To: <mark.hatle@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] Fix gitsm networking and mirroring
Date: Fri, 21 Sep 2018 15:09:50 +0000	[thread overview]
Message-ID: <20180921150949.GZ9430@hiutale> (raw)
In-Reply-To: <70880d62-9114-26fd-ab35-3a32cf8706cb@windriver.com>

On Fri, Sep 21, 2018 at 10:05:14AM -0500, Mark Hatle wrote:
> I looked through my code.  There is an iteration step that happens in the
> unpack.  If the module being asked for (in a given revision) is not present it
> will raise an exception.  This should prevent the 'wrong things' at least.

Thanks! Looking forward to this patch in sumo branch too...

-Mikko

      reply	other threads:[~2018-09-21 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21  0:18 [PATCH] Fix gitsm networking and mirroring Mark Hatle
2018-09-21  0:18 ` [PATCH] fetch2/gitsm.py: Rework the git submodule fetcher Mark Hatle
2018-09-21  7:02 ` [PATCH] Fix gitsm networking and mirroring Mikko.Rapeli
2018-09-21 14:04   ` Mark Hatle
2018-09-21 14:15     ` Mikko.Rapeli
2018-09-21 15:05       ` Mark Hatle
2018-09-21 15:09         ` Mikko.Rapeli [this message]

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=20180921150949.GZ9430@hiutale \
    --to=mikko.rapeli@bmw.de \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mark.hatle@windriver.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