public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
	Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] Make sure git repos are usable inside buildchroot
Date: Wed, 14 Feb 2018 10:59:06 +0100	[thread overview]
Message-ID: <e39dc79f-88cb-0526-e6ca-f00c8d241924@siemens.com> (raw)
In-Reply-To: <d3c954ce-0f26-2f3e-38b1-3461d333edb2@ilbers.de>

On 2018-02-14 10:43, Alexander Smirnov wrote:
> On 02/14/2018 12:30 PM, Henning Schild wrote:
>> There is a similar patch from Alex floating around. My opinion is
> 
> Thanks for the reference ;-)

Sorry, forgot about this.

> 
>> still, this should be fixed upstream and we can wait. After all nobody
>> forces anyone to use git and most git-servers should offer tarballs,
>> which are probably often faster than git.
>>
>> I would rather mark git as broken in the fetcher, but that might just
>> me a result of me not liking git at all ;).
> 
> More easy workaround is also floating on the list:
> 
> https://groups.google.com/forum/#!msg/isar-users/sAcJqSx_vqs/wetXTcMLCQAJ;context-place=forum/isar-users
> 
> 
> Just repack objects to working dir.

But this one is better than everything proposed so far because

a) it's transparent to the user (in contrast to the current bitbake
   proposal)

b) it preservers the efficiency of --shared (in contrast to repacking)

We can easily revert this patch again once bitbake upstream provides a
transparent solution as well.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-02-14  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14  9:14 Jan Kiszka
2018-02-14  9:30 ` Henning Schild
2018-02-14  9:43   ` Alexander Smirnov
2018-02-14  9:59     ` Jan Kiszka [this message]
2018-02-14 19:40 ` [PATCH v2] " Jan Kiszka

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=e39dc79f-88cb-0526-e6ca-f00c8d241924@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.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