From: "Cook, Malcolm" <MEC@stowers.org>
To: "'Ludovic Courtès'" <ludo@gnu.org>
Cc: 'Guix-devel' <guix-devel@gnu.org>
Subject: RE: TIP: untar binary install tarball using option `--warning=no-timestamp`
Date: Fri, 24 Jul 2015 18:33:23 +0000 [thread overview]
Message-ID: <e75dab14908d49619159c7cfc7e5f21d@exchsrv2.sgc.loc> (raw)
In-Reply-To: <878ua6o4hg.fsf@gnu.org>
>
> > Hi, in Cent0S7 vendor supplies me with:
> >
> > tar --version
> > tar (GNU tar) 1.26
>
> Running ‘git blame’ on tar’s src/extract.c shows that warnings about zeroed
> timestamps are no longer issued starting from tar 1.27, released in Oct. 2013.
> I’ve amended the manual to mention that.
Great- thanks - living and learning -
> > Is there some good practice for following activity on debbugs at
> > http://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix#searchoptions
> > It would be great to get an RSS feed or something allowing to watch all new
> bugs and activity on selected "watched" bugs. Any such thing exists?
>
> One can subscribe to bug-guix@gnu.org (or via
> <http://dir.gmane.org/gmane.comp.gnu.guix.bugs>) and see all the activity
> on all the bugs.
Gmane to the rescue again. Of course! NNTP still lives. Hoorah!
> Alternately, if someone only interested in the bug they reported will
> automatically receive followups and status change notifications specifically
> for that bug, on the XYZ@debbugs.gnu.org email address.
Splendid.
> HTH,
Mucho!
~Malcolm
> Ludo’.
prev parent reply other threads:[~2015-07-24 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 18:37 TIP: untar binary install tarball using option `--warning=no-timestamp` Cook, Malcolm
2015-07-22 21:49 ` Ludovic Courtès
2015-07-22 22:10 ` Cook, Malcolm
2015-07-23 23:10 ` Ludovic Courtès
2015-07-24 18:33 ` Cook, Malcolm [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e75dab14908d49619159c7cfc7e5f21d@exchsrv2.sgc.loc \
--to=mec@stowers.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).