git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matt McCutchen" <hashproduct@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: More detailed error messages for snapshot format
Date: Tue, 24 Jul 2007 17:50:29 -0400	[thread overview]
Message-ID: <3bbc18d20707241450y48ef0485i2809c632ac2e643@mail.gmail.com> (raw)
In-Reply-To: <11853108372532-git-send-email-jnareb@gmail.com>

On 7/24/07, Jakub Narebski <jnareb@gmail.com> wrote:
> Improve error messages for snapshot format in git_snapshot:
> distinguish between situation where snapshots are turned off, where
> snapshot format ('sf') parameter is invalid, where given snapshot
> format does not exist in %known_snapshot_formats hash, and where
> gitweb was given unsupported snapshot format.
>
> While at it, use first from all supported snapshots format as default,
> if no snapshot format was provided.

I tested the patch and it worked properly: the errors appeared at the
appropriate times and the first supported format was used as the
default.

I also noticed that the check for an "invalid" format requires that it
contain at least one good character, not that it contain no bad
characters, which was what I originally meant.  It would be nice to
fix the check, or the check could even be removed altogether since
gitweb refuses any format that isn't in %known_snapshot_formats .  (I
think I was misguidedly paranoid to add it in the first place.)

  reply	other threads:[~2007-07-24 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 21:00 [PATCH] gitweb: More detailed error messages for snapshot format Jakub Narebski
2007-07-24 21:50 ` Matt McCutchen [this message]
2007-07-24 23:19   ` [PATCH (amend)] " Jakub Narebski

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=3bbc18d20707241450y48ef0485i2809c632ac2e643@mail.gmail.com \
    --to=hashproduct@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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).