From: "halamour at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/30991] New: Bug 30010 - srcfiles tarball feature
Date: Mon, 23 Oct 2023 18:36:46 +0000 [thread overview]
Message-ID: <bug-30991-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30991
Bug ID: 30991
Summary: Bug 30010 - srcfiles tarball feature
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: halamour at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Following the implementation of PR30000, it may be useful to implement an
addition that fetches all source files related to a program, places them in a
tarball/zip and sends that to stdout. This may be done using srcfiles to fetch
the source files, then libarchive to tarball.
% eu-srcfiles --zip deadbeef > file.zip
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-10-23 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 18:36 halamour at redhat dot com [this message]
2023-10-25 18:49 ` [Bug debuginfod/30991] " halamour at redhat dot com
2024-02-06 2:44 ` amerey at redhat dot com
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=bug-30991-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).