All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Ludwig Nussel <ludwig.nussel@suse.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: allow space as delimiter in mime.types
Date: Tue, 14 Jun 2011 07:59:10 -0700 (PDT)	[thread overview]
Message-ID: <m3ips8v4s2.fsf@localhost.localdomain> (raw)
In-Reply-To: <1308060595-28294-1-git-send-email-ludwig.nussel@suse.de>

Ludwig Nussel <ludwig.nussel@suse.de> writes:

> Subject: [PATCH] gitweb: allow space as delimiter in mime.types

A very minor nitpick: perhaps "work with" rather than "allow" would be
better?

> in openSUSE /etc/mime.types has only spaces. I don't know if there's
> a canonical reference that says that only tabs are allowed. Mutt at
> least also accepts spaces. So make gitweb more liberal too.

Ack.

It is obviously correct, as names of MUME types cannot contain spaces,
it makes gitweb work with openSUSE /etc/mime.types, and it makes code
simpler.

> ---

Signoff (i.e. Signed-off-by)?

>  gitweb/gitweb.perl |    9 +++------
>  1 files changed, 3 insertions(+), 6 deletions(-)
> 
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index 1b83a8d..d81d87b 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -3560,12 +3560,9 @@ sub mimetype_guess_file {
>  	open(my $mh, '<', $mimemap) or return undef;
>  	while (<$mh>) {
>  		next if m/^#/; # skip comments
> -		my ($mimetype, $exts) = split(/\t+/);
> -		if (defined $exts) {
> -			my @exts = split(/\s+/, $exts);
> -			foreach my $ext (@exts) {
> -				$mimemap{$ext} = $mimetype;
> -			}
> +		my ($mimetype, @exts) = split(/\s+/);
> +		foreach my $ext (@exts) {
> +			$mimemap{$ext} = $mimetype;
>  		}
>  	}
>  	close($mh);
> -- 
> 1.7.3.4
> 

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2011-06-14 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 14:09 [PATCH] gitweb: allow space as delimiter in mime.types Ludwig Nussel
2011-06-14 14:59 ` Jakub Narebski [this message]
2011-06-14 19:30   ` J.H.
2011-06-14 21:28   ` Junio C Hamano
2011-06-15  6:10     ` [PATCH v2] " Ludwig Nussel

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=m3ips8v4s2.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ludwig.nussel@suse.de \
    /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.