From: "Andrei Gherzan" <andrei@gherzan.ro>
To: Joe Slater <joe.slater@windriver.com>
Cc: "'openembedded-core@lists.openembedded.org'"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] git repo vs archive for source
Date: Fri, 23 Oct 2020 22:17:02 +0000 (UTC) [thread overview]
Message-ID: <458056c7-059c-4801-ad6d-7637e22f9ea7@gherzan.ro> (raw)
In-Reply-To: <BY5PR11MB3992E2FBAD8DAF232D5321B5881A0@BY5PR11MB3992.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
23 Oct 2020 22:56:28 Joe Slater <joe.slater@windriver.com>:
> When updating versions, like for ruby, say, is it desirable to switch from using “released” archives to using the git(hub) repo with the corresponding branch/tag?
I think git is usually the preferred way mainly because it matches code directly as opposed to a packaged payload.
The exception that I found is when people are using git to store binaries.
--
Andrei Gherzan
[-- Attachment #2: Type: text/html, Size: 926 bytes --]
next prev parent reply other threads:[~2020-10-23 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 21:56 git repo vs archive for source Joe Slater
2020-10-23 22:17 ` Andrei Gherzan [this message]
2020-10-23 23:58 ` [OE-core] " Joshua Watt
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=458056c7-059c-4801-ad6d-7637e22f9ea7@gherzan.ro \
--to=andrei@gherzan.ro \
--cc=joe.slater@windriver.com \
--cc=openembedded-core@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