From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2020, #05; Fri, 18)
Date: Sat, 19 Sep 2020 23:13:27 +0200 [thread overview]
Message-ID: <b7ef3952-872a-40af-0f2e-c392b031a280@web.de> (raw)
In-Reply-To: <xmqqwo0qk0fw.fsf@gitster.c.googlers.com>
Am 19.09.20 um 03:41 schrieb Junio C Hamano:
> * jc/dist-tarball-tweak (2020-09-09) 1 commit
> (merged to 'next' on 2020-09-10 at 36cbe7ee9e)
> + Makefile: allow extra tweaking of distribution tarball
>
> Allow maintainers to tweak $(TAR) invocations done while making
> distribution tarballs.
Just noticed this one. It reminds me of an alternative solution for
archives containing both tracked and untracked files gathering dust on
my disk because I didn't see much demand. It goes the other way and
gives untracked files the same meta data as tracked ones. Interested?
archive: read short blobs in archive.c::write_archive_entry()
archive: add --add-file
Makefile: use git-archive --add-file
Documentation/git-archive.txt | 6 ++
Makefile | 41 ++++++------
archive-tar.c | 22 +------
archive-zip.c | 22 ++-----
archive.c | 117 +++++++++++++++++++++++++++++++---
archive.h | 9 ++-
t/t5000-tar-tree.sh | 29 +++++++++
t/t5003-archive-zip.sh | 28 ++++++++
8 files changed, 203 insertions(+), 71 deletions(-)
--
2.28.0
next prev parent reply other threads:[~2020-09-19 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 1:41 What's cooking in git.git (Sep 2020, #05; Fri, 18) Junio C Hamano
2020-09-19 21:13 ` René Scharfe [this message]
2020-09-19 21:23 ` [PATCH 1/3] archive: read short blobs in archive.c::write_archive_entry() René Scharfe
2020-09-19 21:23 ` [PATCH 2/3] archive: add --add-file René Scharfe
2020-09-19 21:23 ` [PATCH 3/3] Makefile: use git-archive --add-file René Scharfe
2020-09-19 22:35 ` What's cooking in git.git (Sep 2020, #05; Fri, 18) Junio C Hamano
2020-09-20 7:58 ` René Scharfe
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7ef3952-872a-40af-0f2e-c392b031a280@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).