git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] gitweb: Die if there are parsing errors in config file

From
Jakub Narebski <jnareb@gmail.com>
Date
Feb 8, 2010, 08:48 UTC
Message-ID
<201002080948.27094.jnareb@gmail.com>
In-Reply-To
<4B6E9BBB.4000904@eaglescrag.net>
On Sun, 7 Feb 2010, J.H. wrote:
> I'd sign-off that, I've probably run into it a couple of times myself.
> 
> - John 'Warthog9' Hawley
I think you meant ACK, not sign-off...
 
Show 14 quoted lines
> On 02/07/2010 01:40 AM, Jakub Narebski wrote:
> > Otherwise the errors can propagate, and show in damnest places, and
> > you would spend your time chasing ghosts instead of debugging real
> > problem (yes, it is from personal experience).
> > 
> > This follows (parts of) advice in `perldoc -f do` documentation.
> > 
> > Signed-off-by: Jakub Narebski <jnareb@gmail.com>
> > ---
> > This is fallout from my work on [split] "Gitweb output caching" series.
> > Before I used `die $@ if $@;' in t/t9503/test_cache_interface.pl, tests
> > failed for no discernable reason...
> > 
> > So I think the same should be done for the gitweb config file.
[...]
-- 
Jakub Narebski
Poland
Previous: J.H.Next: Jakub Narebski
Message 3 of 6 in “gitweb: Die if there are parsing errors in config file”
  1. gitweb: Die if there are parsing errors in config fileJakub Narebski, Feb 7, 2010
  2. J.H.Feb 7, 2010
  3. Jakub NarebskiFeb 8, 2010
  4. Jakub NarebskiFeb 13, 2010
  5. Junio C HamanoFeb 14, 2010
  6. Jakub NarebskiFeb 14, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.