From: Jakub Narebski <jnareb@gmail.com>
To: "J.H." <warthog19@eaglescrag.net>
Cc: Mark A Rada <marada@uwaterloo.ca>, git@vger.kernel.org
Subject: Re: [PATCHv5] Add Gitweb support for XZ compressed snapshots
Date: Sat, 01 Aug 2009 01:14:35 -0700 (PDT) [thread overview]
Message-ID: <m3zlakq7bt.fsf@localhost.localdomain> (raw)
In-Reply-To: <4A739087.1090301@eaglescrag.net>
"J.H." <warthog19@eaglescrag.net> writes:
> Well you can always call xz with -[1-9] to change the compression
> level (same as gzip and bzip2) though I think a full disabling would
> be 'more' preferable, though I'm not sure I like Jakub's suggestion of
> just deleting it after the fact, it would work.
[...]
The problem is that 'keys %known_snapshot_formats' serves also as list
of allowed snapshot formats, if project specific override is enabled.
We can add another optional flag ('disabled' => 1) if you don't want
to delete from %known_snapshot_formats in $GITWEB_CONFIG, though I
don't know if it is worth it. Anyway such mechanism can be added, and
IMHO should be added, in a separate commit.
> I think more my concern is more what's enabled by default, and since
> xz is still new (as was pointed out) it's probably worth only enabling
> if the admin selects it to be enabled.
By default (i.e. as in gitweb in git.git) 'snapshot' feature has
disabled projects specific override. Which means only 'tgz' snapshot
is enabled / used.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-08-01 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 0:40 [PATCHv5] Add Gitweb support for XZ compressed snapshots Mark A Rada
2009-08-01 0:47 ` J.H.
2009-08-01 8:12 ` demerphq
2009-08-01 9:08 ` Jakub Narebski
2009-08-01 10:13 ` demerphq
2009-08-02 23:25 ` Jakub Narebski
2009-08-02 23:55 ` demerphq
2009-08-03 0:27 ` Jakub Narebski
[not found] ` <9b18b3110908010413w51e901dfk5a6f1666e5c3197f@mail.gmail.com>
2009-08-03 17:26 ` Working on gitweb (was: [PATCHv5] Add Gitweb support for XZ compressed snapshots) Jakub Narebski
2009-08-01 8:14 ` Jakub Narebski [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zlakq7bt.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=marada@uwaterloo.ca \
--cc=warthog19@eaglescrag.net \
/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 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.