[GitHub] log4net pull request: Mono improvements

2014-10-17 Thread antoniusriha
GitHub user antoniusriha opened a pull request:

https://github.com/apache/log4net/pull/11

Mono improvements

This PR
 * introduces mono-4.0 as supported target platform,
 * fixes a casing issue with two source files and
 * fixes a unit test

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/antoniusriha/log4net mono-improvements

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/11.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #11


commit ace6fd9636b525c22def3f9e694e8a1dc67f3aee
Author: Antonius Riha antoniusr...@gmail.com
Date:   2014-10-17T21:14:39Z

Add support for mono-4.0 build

commit 9a513df3da162b1f86f8d5a0df787e43c87225d9
Author: Antonius Riha antoniusr...@gmail.com
Date:   2014-10-17T21:52:33Z

Fix msbuild build on case sensitive platforms

commit a5ef9a50d0c5b5b19e2e42fb717fe549783b716c
Author: Antonius Riha antoniusr...@gmail.com
Date:   2014-10-17T21:54:23Z

Fix XmlLayout brackets test




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: Supporting Log4Net on ASP.NET vNext

2014-10-17 Thread Stefan Bodewig
Hi

as Dominik said, the best place to discuss technical issues around
chages to log4net is this mailing list itself.

On 2014-10-15, Kanchan Mehrotra wrote:

 We would like to discuss with you plans for releasing support for your
 package for ASP.NET vNext

What kind of changes would log4net need to make so you can support it?

 As a part of our testing to understand the porting experience to
 ASP.NET vNext we ported some parts of your package source to use the
 latest preview release of ASP.NET vNext. We would like to share our
 initial investigations with you.

Great, let's hear about them.

 so please do let me know who on the project owners team should we
 involve in these discussions

Please understand that there is a team of people who work on log4net
code - and not really that actively, to be honest - but we don't
consider ourselves owners.  The term sounds wrong in the context of an
Apache project :-)

Part of our (Apache's) culture is a if it didn't happen on the mailing
list it didn't happen mantra.  Please don't hesitate to bring anything
you want to discuss/explain here and let's go from there.

Cheers

Stefan


RE: Supporting Log4Net on ASP.NET vNext

2014-10-17 Thread Kanchan Mehrotra
Thanks folks!
We are wondering if it will be a good idea to have a conference call with some 
of you who are interested to share more information on ASP.NET vNext. We would 
also like to further discuss your plans on porting log4Net to support vNext. 
Can you please suggest how we can proceed on this?

-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org] 
Sent: Friday, October 17, 2014 10:29 PM
To: Log4NET Dev
Cc: Daniel Roth; Jiří Činčura; Kanchan Mehrotra
Subject: Re: Supporting Log4Net on ASP.NET vNext

Hi

as Dominik said, the best place to discuss technical issues around chages to 
log4net is this mailing list itself.

On 2014-10-15, Kanchan Mehrotra wrote:

 We would like to discuss with you plans for releasing support for your 
 package for ASP.NET vNext

What kind of changes would log4net need to make so you can support it?

 As a part of our testing to understand the porting experience to 
 ASP.NET vNext we ported some parts of your package source to use the 
 latest preview release of ASP.NET vNext. We would like to share our 
 initial investigations with you.

Great, let's hear about them.

 so please do let me know who on the project owners team should we 
 involve in these discussions

Please understand that there is a team of people who work on log4net code - and 
not really that actively, to be honest - but we don't consider ourselves 
owners.  The term sounds wrong in the context of an Apache project :-)

Part of our (Apache's) culture is a if it didn't happen on the mailing list it 
didn't happen mantra.  Please don't hesitate to bring anything you want to 
discuss/explain here and let's go from there.

Cheers

Stefan