|
RE: Proposed bug fix for AspNetRequestPatternConverter.Convert() |
|
| Alessandro Ghizzardi |
RE: Proposed bug fix for AspNetRequestPatternConverter.Convert() |
Mon, 02 Apr, 16:58 |
| Ron Grabowski |
Re: Proposed bug fix for AspNetRequestPatternConverter.Convert() |
Wed, 11 Apr, 01:35 |
|
[jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
|
| Piotr Jastrząbek (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Thu, 05 Apr, 14:38 |
| Joshua Masek (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Thu, 05 Apr, 15:54 |
| Johnson, Thomas |
RE: [jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Thu, 05 Apr, 16:07 |
| Stefan Bodewig (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Fri, 06 Apr, 05:31 |
| Ryan Boggs |
Re: [jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Fri, 06 Apr, 06:55 |
| Stefan Bodewig (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Fri, 06 Apr, 05:38 |
| Piotr Jastrząbek (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Mon, 09 Apr, 21:53 |
| Joshua Masek (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Tue, 10 Apr, 16:07 |
|
[jira] [Commented] (LOG4NET-266) AdoNetAppender does not work on a IIS 7 website using Windows authentication |
|
| Johannes Krackowizer (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-266) AdoNetAppender does not work on a IIS 7 website using Windows authentication |
Thu, 05 Apr, 21:36 |
| Ron Grabowski (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-266) AdoNetAppender does not work on a IIS 7 website using Windows authentication |
Wed, 11 Apr, 01:25 |
| Stefan Bodewig (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. |
Fri, 06 Apr, 05:32 |
| Petr Vones (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-64) [PATCH] to RollingFileAppender.cs to add the ability to preserve the log file name extension when rolling the log file. |
Sat, 07 Apr, 21:52 |
| Petr Vones (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-64) [PATCH] to RollingFileAppender.cs to add the ability to preserve the log file name extension when rolling the log file. |
Sat, 07 Apr, 21:52 |
| Andy Smith (Created) (JIRA) |
[jira] [Created] (LOG4NET-331) AdoNetAppender errors when writing Asp.net item when Request object is null |
Mon, 09 Apr, 21:11 |
| Ron Grabowski (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-331) AdoNetAppender errors when writing Asp.net item when Request object is null |
Wed, 11 Apr, 01:11 |
| George Chung |
Re: [jira] [Commented] (LOG4NET-331) AdoNetAppender errors when writing Asp.net item when Request object is null |
Wed, 11 Apr, 01:34 |
| Andy Smith (Updated) (JIRA) |
[jira] [Updated] (LOG4NET-331) AdoNetAppender errors when writing Asp.net item when Request object is null |
Mon, 09 Apr, 21:11 |
| stalinsubash (Created) (JIRA) |
[jira] [Created] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Tue, 10 Apr, 09:10 |
| stalinsubash (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Wed, 18 Apr, 10:59 |
| Ron Grabowski |
Re: [jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Thu, 19 Apr, 04:47 |
| Andrew Arnott (Created) (JIRA) |
[jira] [Created] (LOG4NET-333) AssemblyVersionAttribute should specify less precise version |
Tue, 10 Apr, 13:59 |
|
[jira] [Closed] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
|
| Ron Grabowski (Closed) (JIRA) |
[jira] [Closed] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Wed, 11 Apr, 00:39 |
| Ron Grabowski (Closed) (JIRA) |
[jira] [Closed] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Thu, 12 Apr, 04:26 |
|
[jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
|
| Ron Grabowski (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Wed, 11 Apr, 00:47 |
| stalinsubash (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Wed, 11 Apr, 07:26 |
| Ron Grabowski (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Thu, 19 Apr, 04:27 |
| stalinsubash (Created) (JIRA) |
[jira] [Created] (LOG4NET-334) Appender Faill over |
Wed, 11 Apr, 08:06 |
| Dominik Psenner (Resolved) (JIRA) |
[jira] [Resolved] (LOG4NET-334) Appender Faill over |
Wed, 11 Apr, 08:24 |
| Johannes Krackowizer (Updated) (JIRA) |
[jira] [Updated] (LOG4NET-266) AdoNetAppender does not work on a IIS 7 website using Windows authentication |
Wed, 11 Apr, 11:36 |
| stalinsubash (Reopened) (JIRA) |
[jira] [Reopened] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders |
Thu, 12 Apr, 04:16 |
| Simon Svensson (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-328) Log4Net for Windows 2008 64bit machine |
Thu, 12 Apr, 09:37 |
| Simon Svensson (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-328) Log4Net for Windows 2008 64bit machine |
Thu, 12 Apr, 09:37 |
| Simon Svensson (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-333) AssemblyVersionAttribute should specify less precise version |
Thu, 12 Apr, 09:41 |
| Simon Svensson (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-333) AssemblyVersionAttribute should specify less precise version |
Thu, 12 Apr, 09:43 |
|
[jira] [Commented] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables. |
|
| Simon Svensson (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables. |
Thu, 12 Apr, 10:37 |
| Ron Grabowski (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables. |
Thu, 12 Apr, 23:41 |
|
[jira] [Issue Comment Edited] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables. |
|
| Simon Svensson (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables. |
Thu, 12 Apr, 10:37 |
| Simon Svensson (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables. |
Thu, 12 Apr, 10:37 |
| Ron Grabowski (Assigned) (JIRA) |
[jira] [Assigned] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables. |
Thu, 12 Apr, 23:31 |
| Ron Grabowski (Updated) (JIRA) |
[jira] [Updated] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables. |
Thu, 12 Apr, 23:41 |
|
[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile |
|
| Rufus Buschart (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Fri, 13 Apr, 11:33 |
| Dominik Psenner (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Fri, 13 Apr, 21:37 |
| Stefan Bodewig (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Sat, 14 Apr, 04:11 |
| Rufus Buschart (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Mon, 16 Apr, 07:34 |
| Dominik Psenner (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Mon, 16 Apr, 09:02 |
| Rufus Buschart (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Mon, 16 Apr, 10:46 |
| Dominik Psenner (Commented) (JIRA) |
[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Mon, 16 Apr, 11:40 |
|
[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile |
|
| Rufus Buschart (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Fri, 13 Apr, 11:33 |
| Dominik Psenner (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Fri, 13 Apr, 21:39 |
| Dominik Psenner (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Fri, 13 Apr, 22:45 |
| Dominik Psenner (Issue Comment Edited) (JIRA) |
[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile |
Mon, 16 Apr, 11:42 |
| bernard mcgourty (JIRA) |
[jira] [Created] (LOG4NET-335) Lost the ability to monitor changes to logger config files when you call ConfigureAndWatch multiple times with different Config File Names - worked fine on 1.2.10.0 |
Thu, 26 Apr, 00:23 |
| bernard mcgourty (JIRA) |
[jira] [Created] (LOG4NET-336) Enabling ImmediateFlush on a RollingFileAppender has no effect |
Thu, 26 Apr, 15:02 |
| Jens Weiermann (JIRA) |
[jira] [Created] (LOG4NET-337) RollingFileAppender.RollOverIfDateBoundaryCrossing doesn't take PreserveLogFileNameExtension into account |
Mon, 30 Apr, 11:18 |