From: nobody at nowhere.ws (Christian Franke)
Subject: Snapshots mtime breaks digests
Date: Fri, 27 Apr 2012 15:50:59 +0200 [thread overview]
Message-ID: <4F9AA443.70007@nowhere.ws> (raw)
In-Reply-To: <CAEik5nPEmYaih+eMKQ1WtP6-_y201MTpH=gmGJV6QmGfG4eEkg@mail.gmail.com>
On 04/27/2012 01:42 PM, Dan McGee wrote:
>> On 27-04-12 04:14, Adrian C. wrote:
>>> I use cgit release 0.9.0.2 with Lighttpd frontend and snapshots enabled
>>> on http://git.sysphere.org I presume the mtime changes when the original
>>> tarball expires from the Cgit cache and I didn't find anything in the
>>> cgitrc manual so far.
>>>
>>> Anyone knows of a workaround I can apply to keep these folks happy?
>>> Thanks.
>
> Use anything except gzip; it is the only one having a silly field like
> this. xz did not make this same mistake. Note that the `gzip -n`
> program option will prevent this from being included (and thus
> changing); not sure if you could patch cgit to generate tarballs in
> this fashion.
Couldn't the date also be based on the time of the last change?
Best Regards,
Christian Franke
next prev parent reply other threads:[~2012-04-27 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 2:14 anrxc
2012-04-27 8:03 ` mailings
2012-04-27 11:42 ` dpmcgee
2012-04-27 13:50 ` nobody [this message]
2012-04-28 0:43 ` anrxc
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=4F9AA443.70007@nowhere.ws \
--to=cgit@lists.zx2c4.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.
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 NNTP newsgroup(s).