($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "André Draszik" <andre.draszik@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [bitbake][PATCH 0/3] support git's safe.bareRepository=explicit
Date: Mon, 19 Feb 2024 13:25:37 +0000	[thread overview]
Message-ID: <9bfd5d27a3cd662380a4a7340026ff2a4a744b40.camel@linaro.org> (raw)
In-Reply-To: <33c2021c9e0bad9fc287aa7af8070e1a9cdbc5e7.camel@linuxfoundation.org>

Hi Richard,

On Mon, 2024-02-19 at 12:08 +0000, Richard Purdie wrote:
> Thanks. I'm not thrilled to need to do this and we probably do need a
> better solution but a stop gap does help.

I had some issues with failing selftests when I converted to --git-dir= initially
instead of the patches here, so I went for this solution as a quicker alternative
for now.

> It may be an idea to file a bug so we don't forget we need to improve
> things?

https://bugzilla.yoctoproject.org/show_bug.cgi?id=15405

Cheers,
Andre'



      reply	other threads:[~2024-02-19 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  9:52 [bitbake][PATCH 0/3] support git's safe.bareRepository=explicit André Draszik
2024-02-19  9:52 ` [bitbake][PATCH 1/3] fetch/git2: support git's safe.bareRepository André Draszik
2024-02-19  9:52 ` [bitbake][PATCH 2/3] tests/fetch: " André Draszik
2024-02-19  9:52 ` [bitbake][PATCH 3/3] git-make-shallow: " André Draszik
2024-02-19 12:08 ` [bitbake-devel] [bitbake][PATCH 0/3] support git's safe.bareRepository=explicit Richard Purdie
2024-02-19 13:25   ` André Draszik [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=9bfd5d27a3cd662380a4a7340026ff2a4a744b40.camel@linaro.org \
    --to=andre.draszik@linaro.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).