From: Jakub Narebski <jnareb@gmail.com>
To: Mark A Rada <marada@uwaterloo.ca>
Cc: git@vger.kernel.org
Subject: Re: Add Gitweb support for LZMA compressed snapshots
Date: Thu, 30 Jul 2009 01:31:28 -0700 (PDT) [thread overview]
Message-ID: <m3r5vy1siq.fsf@localhost.localdomain> (raw)
In-Reply-To: <E0C39B59-E2C5-4C28-9570-D33FEA2A44EB@uwaterloo.ca>
Mark A Rada <marada@uwaterloo.ca> writes:
> I thought I would submit this little patch I made to my gitweb. I am
> on a relatively slow connection, and so LZMA compression time is
> less of a concern than bandwidth---I'm guessing that I am not the
> only person who suffers from slow internet connection syndrome.
First, Documentation/SubmittingPatches states that we prefer inline
patches, with additional comments (like the one above) either between
"---\n" line and diffstat, or like I did here before patch with patch
separated by comment by e.g. "-- >8 --\n" (scissors) line.
If posting patch inline isn't possible, and you have to use
attachement (for example because mailer you use wraps lines), please
at least use 'text/plain' mimetype so patch can be viewed without need
to save it in separate file (this might require changing suffix from
'.patch' to '.txt').
Second, if you are using 'txz' as internal name for new snapshot
format, why not use 'XZ utils' instead of 'LZMA Utils', and use
'display' => 'txz', 'type' => 'application/x-xz' and
'suffix' => '.txz' (BTW. shouldn't suffix in your case be '.tar.lzma'
and not only '.lzma'?) and of course 'compressor' => ['xz']?
BTW. I wonder if it would be good idea to add support for this format
directly to git-archive... OTOH it would mean additional dependency.
--
Jakub Narebski
Git User's Survey 2009: http://tinyurl.com/GitSurvey2009
-- >8 --
From: Mark Rada <marada@uwaterloo.ca>
Subject: [PATCH] Add Gitweb support for LZMA compressed snapshots
Signed-off-by: Mark Rada <marada@uwaterloo.ca>
---
gitweb/gitweb.perl | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 38492d0..e131ea4 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -184,6 +184,13 @@ our %known_snapshot_formats = (
'format' => 'tar',
'compressor' => ['bzip2']},
+ 'txz' => {
+ 'display' => 'tar.lzma',
+ 'type' => 'application/x-lzma',
+ 'suffix' => '.lzma',
+ 'format' => 'tar',
+ 'compressor' => ['lzma']},
+
'zip' => {
'display' => 'zip',
'type' => 'application/x-zip',
@@ -196,6 +203,7 @@ our %known_snapshot_formats = (
our %known_snapshot_format_aliases = (
'gzip' => 'tgz',
'bzip2' => 'tbz2',
+ 'lzma' => 'txz',
# backward compatibility: legacy gitweb config support
'x-gzip' => undef, 'gz' => undef,
--
1.6.4
next prev parent reply other threads:[~2009-07-30 8:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 5:48 Add Gitweb support for LZMA compressed snapshots Mark A Rada
2009-07-30 7:44 ` J.H.
2009-08-01 7:43 ` Alex Riesen
2009-08-01 14:34 ` Dmitry Potapov
2009-08-01 14:38 ` André Goddard Rosa
2009-08-01 14:58 ` Jim Meyering
2009-08-01 18:51 ` Alex Riesen
2009-07-30 7:52 ` Johannes Schindelin
2009-07-30 8:31 ` Jakub Narebski [this message]
2009-07-30 8:43 ` Johannes Schindelin
2009-07-31 15:45 ` Felipe Contreras
2009-08-01 12:34 ` Johannes Schindelin
2009-08-01 13:10 ` Felipe Contreras
2009-08-01 14:04 ` Erik Faye-Lund
2009-08-01 16:07 ` Mark A Rada
2009-08-01 21:39 ` Erik Faye-Lund
2009-08-01 14:13 ` Dmitry Potapov
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=m3r5vy1siq.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=marada@uwaterloo.ca \
/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).