From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19481@debbugs.gnu.org
Subject: bug#19481: package.el: support .tar archives featuring a pax_global_header entry
Date: Mon, 20 Jan 2020 13:35:29 -0500 [thread overview]
Message-ID: <jwvwo9m9dzw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3mui5xu7c.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 25 Jun 2019 22:53:43 +0200")
> It doesn't look like these changes were applied -- are they still of
> interest, or is the pax_global_header entry not supported any more?
Yes, they are definitely still relevant and should be applied. I think
they've not been applied simply because we were waiting for the tests.
BTW, I do have some minor comment about the suggested patch: while
I think the `filter` argument makes sense as a new feature for
`tar-untar-buffer`, I'm not completely sure that exposing pax's internal
details to this filter is a good idea. Part of the reason I'm not sure
is because I'm not sufficiently familiar with the content of these "type
55" entries. But if it's used for extra metadata (or something like
that), then it should be ignored by default rather than only if you pass
an appropriate filter function.
Stefan
next prev parent reply other threads:[~2020-01-20 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 17:55 bug#19481: package.el: support .tar archives featuring a pax_global_header entry Ivan Shmakov
2015-01-01 18:27 ` Eli Zaretskii
2015-01-01 18:49 ` Ivan Shmakov
2015-01-28 20:54 ` Ivan Shmakov
2015-01-31 8:41 ` Eli Zaretskii
2015-01-31 11:05 ` Ivan Shmakov
2015-01-31 11:22 ` Eli Zaretskii
2015-02-07 20:10 ` bug#19481: new tar-header-extractable-p, to use in tar-untar-buffer Ivan Shmakov
2015-02-07 20:26 ` Eli Zaretskii
2016-02-23 11:30 ` Lars Ingebrigtsen
2019-06-25 20:53 ` bug#19481: package.el: support .tar archives featuring a pax_global_header entry Lars Ingebrigtsen
2020-01-20 18:35 ` Stefan Monnier [this message]
2020-08-13 9:01 ` Lars Ingebrigtsen
2020-08-19 13:42 ` Lars Ingebrigtsen
2015-01-01 18:38 ` Dmitry Gutov
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=jwvwo9m9dzw.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19481@debbugs.gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.