From: Mark Rada <marada@uwaterloo.ca>
To: Sam Vilain <sam@vilain.net>
Cc: Mark Rada <marada@uwaterloo.ca>,
Jakub Narebski <jnareb@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [RFC/PATCH 1/3] gitweb: make suspenders more useful
Date: Sun, 23 Aug 2009 18:39:14 -0400 [thread overview]
Message-ID: <4A91C512.7000707@mailservices.uwaterloo.ca> (raw)
In-Reply-To: <4A91BE50.7070103@vilain.net>
On 23/08/09 6:10 PM, Sam Vilain wrote:
> Mark Rada wrote:
>> Subject: [RFC/PATCH 1/3] gitweb: make suspenders more useful
>
> Suspenders? Really?
>
> Sam
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Context:
On 21/08/09 5:43 PM, Junio C Hamano wrote:
> Mark A Rada <marada@uwaterloo.ca> writes:
>
>> Unless I missed a case, the tests show that the extra condition check
>> that was added in the &git_snapshot routine is never actually executed,
>> because a disabled snapshot format is not added to @snapshot_fmts, which
>> is checked first.
>>
>> snippet:
>> 5178 } elsif (!grep($_ eq $format, @snapshot_fmts)) {
>> 5179 die_error(403, "Unsupported snapshot format");
>> 5180 } elsif ($known_snapshot_formats{$format}{'disabled'}) {
>> 5181 die_error(403, "Snapshot format not allowed");
>> 5182 }
>> 5183
>
> True; filter_snapshot_fmts looks at 'disabled' first.
>
> I do not mind keeping these two lines as belt-and-suspender, though.
>
Yup...I couldn't think of an appropriate title and I expect this
patch to be edited (for another reason) or thrown out anyways.
--
Mark A Rada (ferrous26)
marada@uwaterloo.ca
next prev parent reply other threads:[~2009-08-23 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 21:53 [RFC/PATCH 1/3] gitweb: make suspenders more useful Mark Rada
2009-08-23 22:10 ` Sam Vilain
2009-08-23 22:39 ` Mark Rada [this message]
2009-08-23 22:48 ` Sam Vilain
2009-08-24 3:09 ` [RFC/PATCH 1/3] gitweb: improve snapshot error handling Mark Rada
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=4A91C512.7000707@mailservices.uwaterloo.ca \
--to=marada@uwaterloo.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=sam@vilain.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.