From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Andreas Grünbacher" <andreas.gruenbacher@gmail.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Apply git bundle to source tree?
Date: Sat, 19 Sep 2020 19:28:52 +0000 [thread overview]
Message-ID: <20200919192852.GG67496@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAHpGcMJy=0deaByZ=jXHRiHgHH7utHc0JTG=BMq9Yf1DOKvuGw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
On 2020-09-18 at 21:45:01, Andreas Grünbacher wrote:
> What I had in mind were actually distro packages: most projects
> nowadays live somewhere in git repositories. When they're packaged,
> this usually results in a source package with a diff on top of a
> baseline release, so the commit history is lost. Friendly packagers
> include the commit hashes and point users to a suitable git
> repository, but that's not enforced or consistent. Including the
> actual git history in packages would be much nicer (i.e., a git
> bundle), but if that can't replace the patch as well, it's rather
> unlikely to happen.
Debian considered using Git as part of the 3.0 (git) format, but the
problem with that is that some upstreams include non-free or
undistributable material in their repositories, and obviously Debian
can't distribute such software in main. Tarballs can be repacked, but
it's harder to rewrite Git history to exclude objects.
I do think the idea is cool and it would be a neat application, but
distributing the source history of an upstream project is tricky for
for packagers for practical reasons.
--
brian m. carlson: Houston, Texas, US
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2020-09-19 19:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 11:13 Apply git bundle to source tree? Andreas Grünbacher
2020-09-18 14:02 ` Taylor Blau
2020-09-18 14:12 ` Andreas Grünbacher
2020-09-18 14:17 ` Taylor Blau
2020-09-18 14:50 ` Andreas Grünbacher
2020-09-18 15:21 ` Andreas Schwab
2020-09-18 15:32 ` Andreas Grünbacher
2020-09-18 15:52 ` Andreas Schwab
2020-09-18 15:41 ` Junio C Hamano
2020-09-18 20:00 ` Andreas Grünbacher
2020-09-18 20:18 ` Konstantin Ryabitsev
2020-09-18 21:45 ` Andreas Grünbacher
2020-09-19 12:06 ` Thomas Guyot-Sionnest
2020-09-19 19:28 ` brian m. carlson [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=20200919192852.GG67496@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=andreas.gruenbacher@gmail.com \
--cc=git@vger.kernel.org \
--cc=konstantin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.