Hi all
as the subject says. I'd really like to cut the 2.0.6 release soonish
but without anybody testing what we currently have this may just end up
in a useless exercise of the release process.
Stefan
Time flies and as always spare time is rare. There is once a lot of work
related stuff to do and I cant swim fast enough to reach the shore. Please
give me more time.
On 12 Oct 2016 11:53 a.m., "Stefan Bodewig" wrote:
Hi all
as the subject says. I'd really like to cut the 2.0.6 release soonish
On 2016-10-12, Dominik Psenner wrote:
> Time flies and as always spare time is rare. There is once a lot of work
> related stuff to do and I cant swim fast enough to reach the shore. Please
> give me more time.
Oh, I fully understand that, we are in the same boat most of the
time. Take your time.
Github user Salgat commented on the issue:
https://github.com/apache/log4net/pull/25
Any news if this will ever get pulled?
---
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
enable
Yep, i am going to do regression tests. Setting up .net core projects is
far from possible with the available time.
On 12 Oct 2016 5:11 p.m., "Stefan Bodewig" wrote:
> On 2016-10-12, Dominik Psenner wrote:
>
> > Time flies and as always spare time is rare. There is once a lot of work
> > related
The patch looks sensible. Whats your opinion stefan?
On 12 Oct 2016 7:42 p.m., "Salgat" wrote:
> Github user Salgat commented on the issue:
>
> https://github.com/apache/log4net/pull/25
>
> Any news if this will ever get pulled?
>
>
> ---
> If your project is set up for it, you can reply
On 2016-10-06, Raymond Sanchez wrote:
> I went to nuget.org and I don't see a beta version for log4net for the
> current work.
> If we have a beta version, more developers can get involved with testing
> the latest version.
At the ASF even a beta release is a release which requires a vote.
One
On 2016-10-12, Dominik Psenner wrote:
> The patch looks sensible. Whats your opinion stefan?
all the whitespace changes are distracting. And the patch contains
changes that are completely unrelated - it seems to contain pull request
#24 as well.
I'll comment on the PR.
Stefan
Github user bodewig commented on the issue:
https://github.com/apache/log4net/pull/25
This PR seems to include #24 as well, could you provide a patch without it?
Also, I'm not sure why `Flush` has been added to `ILoggerRepository`
directly. It would be better if `LoggerReposit
Github user JJoe2 commented on the issue:
https://github.com/apache/log4net/pull/25
Hi Stefan,
Thanks for the feedback.
As youâll have gathered Iâm a novice as far as Git and Github are
concerned, though slightly less so than I was when I created this patch.
Github user bodewig commented on the issue:
https://github.com/apache/log4net/pull/25
I've ensured all line-ends are consistent and set to native in svn trunk -
git is not our primary repository,
https://svn.apache.org/repos/asf/logging/log4net/trunk/ is. If you've got
access to svn
11 matches
Mail list logo
