Hi Davyd,
On Thu, 29 Feb 2024 at 12:29, Davyd McColl wrote:
> Jan, Volkan brings up one of the sticky points - signing the release -
> which I can do from my personal
>
> machine, with the binary artifacts in place - so I could do steps 3 and
> 4 (build and sign) - but I'll only
This is just a c
Hi Piotr
I actually don't know with 100% accuracy, but I did find this:
https://www.mitchelsellers.com/blog/article/net-5-deterministic-builds-source-linking
which is a little old but might be worthwhile investigating.
-d
On 29 February 2024 13:54:47 "Piotr P. Karwasz"
wrote:
Hi Davyd,
Hi,
as far as i know, setting true in csproj should
be enough for this.
See line 73 in
https://github.com/apache/logging-log4net/pull/115/files#diff-0f81264aa7e82fb31702de904a86565584da1349835af0d3b08b69d09502a384
Regards.
Jan
Thursday, February 29, 2024, 1:12:24 PM, you wrote:
> Hi Pi
Hi,
thanks for the opportunity, I will try my best.
https://github.com/apache/logging-log4net/pull/115
Regards.
Jan
Thursday, February 29, 2024, 12:26:55 PM, you wrote:
> Hi Volkan
> If Jan feels up to the task, it would be worthwhile to give it a go. If
> nothing else, it
cedure steps over chat could save both of
you from long waiting times.
I am looking forward to the outcome! 🤞
On Thu, Feb 29, 2024 at 8:56 PM Jan Friedrich wrote:
> Hi,
>
> thanks for the opportunity, I will try my best.
>
> https://github.com/apache/logging-log4net/pull/115
Dear all:
Will you please let me know how to opt-out from emails?
Thank you,
Harry
-Original Message-
From: rgo...@apache.org
Sent: Saturday, April 4, 2020 5:16 PM
To: comm...@logging.apache.org
Subject: svn commit: r1058827 -
/websites/production/logging/content/log4net/log4net
org
> Sent: Saturday, April 4, 2020 5:16 PM
> To: comm...@logging.apache.org
> Subject: svn commit: r1058827 -
> /websites/production/logging/content/log4net/log4net-2.0.8/index.html
>
> Author: rgoers
> Date: Sun Apr 5 00:15:38 2020
> New Revision: 1058827
>
>
vision: 1065013
>
> Log:
> :memo: update download doc
>
> Modified:
>
> websites/production/logging/content/log4net/log4net-2.0.9/download_log4net.html
>
> Modified:
> websites/production/logging/conten
[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118230#comment-16118230
]
Georgi Zhelezarov commented on LOG4NET-558:
---
Hello ,
i managed to repro
[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georgi Zhelezarov updated LOG4NET-558:
--
Attachment: ConsoleApp1.zip
Test application that prints a few lines with and without
Blake created LOG4NET-578:
-
Summary: Type is not resolved for member
'log4net.Util.PropertiesDictionary,log4net
Key: LOG4NET-578
URL: https://issues.apache.org/jira/browse/LOG4NET-578
Project: Lo
Husain Alshehhi created LOG4NET-576:
---
Summary: Documentation on turning log4net internal debug with
dotnet core
Key: LOG4NET-576
URL: https://issues.apache.org/jira/browse/LOG4NET-576
Project
[
https://issues.apache.org/jira/browse/LOG4NET-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165822#comment-16165822
]
Dominik Psenner commented on LOG4NET-576:
-----
log4net can be configured in var
Hi,
our CI is ready to supply us with binaries along with the log4net
website. This will be the first time that binaries from the CI are
shipped as a release. Therefore we seek out for volunteers who evaluate
the CI binaries [1]. Doing so is a great help and allows us to take the
next steps
It is not abandoned; it is in need of more developers. One of the more
active developers of that project is currently ill, however, and most
of the rest of us here aren't that familiar with .NET. I do have
intentions to try and make a release soon, though, but I'm not that
familiar with the codebas
n the foreseeable future.
To repopulate the set of developers we could lower the bar for adding new
committers. We could also push log4net back to incubation. What do you
think?
--
Dominik Psenner
On Fri, Jun 28, 2019, 17:22 Matt Sicker wrote:
> It is not abandoned; it is in need of more developers
On Sat, Jun 29, 2019 at 1:21 PM Dominik Psenner wrote:
> We could also push log4net back to incubation. What do you think?
If availability of people is an issue, then this would be an excellent
way of exhausting those even more.
Jochen
,
wrote:
> On Sat, Jun 29, 2019 at 1:21 PM Dominik Psenner
> wrote:
> > We could also push log4net back to incubation. What do you think?
>
> If availability of people is an issue, then this would be an excellent
> way of exhausting those even more.
>
> Jochen
>
I had this message in draft for quite some time now and just now I decided
to send it in a slightly modified version.
While log4net has been around for a while it may have come the point in
time when it has reached end of life. A good indicator to me is the number
of active contributors. This
ominik Psenner
Sent: Monday, September 16, 2019 5:10:50 PM
To: dev@logging.apache.org
Subject: Re: Is Log4Net project abandoned?
I had this message in draft for quite some time now and just now I decided
to send it in a slightly modified version.
While log4net has been around for a while it ma
t; Mike
>
> Get Outlook for iOS<https://aka.ms/o0ukef>
>
> From: Dominik Psenner
> Sent: Monday, September 16, 2019 5:10:50 PM
> To: dev@logging.apache.org
> Subject: Re: Is Log4Net project abandoned?
>
> I had this message in
Streamlining the architectures across the different log4* implementations
has been discussed earlier. It would make sense to split log4net into
several libraries (api, configuration, several appender.xxx, etc). Further
make these assemblies all available over nuget. I could imagine this to
become
Hi Dominik,
I have in the past been much interested in log4net and, as you may
remember, I hoped to integrate log4net.ext.json. (Un)fortunately, life
goes on and I'm not in the .net realm anymore to be of any benefit
here. Like you, I struggle to maintain the extension I wrote. If
so
Hi Dominik,
I can allocate some time to help setting up the builds for Log4Net. Let me
know what tasks I can start with.
I would suggest https://dev.azure.com as a replacement for NAnt. The azure
pipeline is free for GitHub projects and have support to the latest
frameworks.
Regards,
Kabilan
On
Hi Dominik,
I have setup a sample build for Log4Net.standard solution. Let me know if
its okay to proceed then we can migrate all builds to azure devops.
https://dev.azure.com/logging-log4net/Log4Net/_build/results?buildId=20&view=artifacts
Regards,
Kabilan
On Tue, Oct 1, 2019 at 3:1
I have written a small project that hooks log4net into asp net core
architecture and am looking to publish the package to nuget under the apache
foundation.
Brian
Sent from Outlook<http://aka.ms/weboutlook>
Hi,
I have discovered a problem with "interprocesslock" locking model used in
our project for File appender. I will appreciate if you could investigate
the issue and let me know what is wrong. Maybe it is a bug within log4net
dll.
ISSUE:
If file appender is configured with
&quo
+1
Ralph
> On Apr 4, 2020, at 3:24 PM, Ralph Goers wrote:
>
> I have modified the STATUS.txt and README.txt for Log4Net, tagged the source,
> zipped it and then published it to
> https://dist.apache.org/repos/dist/dev/logging/log4net/
> <https://dist.apache.org/r
+1
Remko.
> On Apr 5, 2020, at 8:50, Ralph Goers wrote:
>
> +1
>
> Ralph
>
>> On Apr 4, 2020, at 3:24 PM, Ralph Goers wrote:
>>
>> I have modified the STATUS.txt and README.txt for Log4Net, tagged the
>> source, zipped it and then published it
+1
On Sun, 5 Apr 2020, 00:25 Ralph Goers wrote:
> I have modified the STATUS.txt and README.txt for Log4Net, tagged the
> source, zipped it and then published it to
> https://dist.apache.org/repos/dist/dev/logging/log4net/ <
> https://dist.apache.org/repos/dist/dev/logging/log4
+1
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Sun, Apr 5, 2020, 09:21 Volkan Yazıcı wrote:
> +1
>
> On Sun, 5 Apr 2020, 00:25 Ralph Goers wrote:
>
> > I have modified the STATUS.txt and README.txt for Log4Net, tagged the
> > so
ph Goers wrote:
> >
> > > I have modified the STATUS.txt and README.txt for Log4Net, tagged the
> > > source, zipped it and then published it to
> > > https://dist.apache.org/repos/dist/dev/logging/log4net/ <
> > > https://dist.apache.org/repos/dist/dev/lo
> >
> > On Sun, Apr 5, 2020, 09:21 Volkan Yazıcı wrote:
> >
> > > +1
> > >
> > > On Sun, 5 Apr 2020, 00:25 Ralph Goers wrote:
> > >
> > > > I have modified the STATUS.txt and README.txt for Log4Net, tagged the
> > > > so
Info about our existing infra is documented here:
https://cwiki.apache.org/confluence/display/INFRA/Jenkins
On Sat, 25 Apr 2020 at 13:38, Davyd McColl wrote:
>
> Hi
>
> Quick question: what operating system does the available CI server run?
> Even if docker is an option, the host system is matter
Thanks for the reply (:
Would external build systems like circleci be acceptable too?
-d
On April 25, 2020 21:03:01 Matt Sicker wrote:
Info about our existing infra is documented here:
https://cwiki.apache.org/confluence/display/INFRA/Jenkins
On Sat, 25 Apr 2020 at 13:38, Davyd McColl wr
The only external build systems that are set up for Apache right now
are Travis and some limited GitHub Action experiments. Other CI
systems may need to talk with Apache Infra.
On Sat, 25 Apr 2020 at 14:47, Davyd McColl wrote:
>
> Thanks for the reply (:
>
> Would external build systems like circ
What would need to be done to make other CI systems talk with Apache Infra?
I ask because I've spend around a day now trying to convince Travis CI to build
log4net successfully, without a lot of joy, particularly because the Travis
Windows build environment is quite out of date, having
o make other CI systems talk with Apache Infra?
>
> I ask because I've spend around a day now trying to convince Travis CI to
> build log4net successfully, without a lot of joy, particularly because the
> Travis Windows build environment is quite out of date, having been launched
e Infra?
> >
> > I ask because I've spend around a day now trying to convince Travis CI to
> > build log4net successfully, without a lot of joy, particularly because the
> > Travis Windows build environment is quite out of date, having been launched
> > as a beta
o create a Jira
> > ticket in https://issues.apache.org/jira/browse/INFRA
> >
> > On Mon, 27 Apr 2020 at 01:28, Davyd McColl wrote:
> > >
> > > What would need to be done to make other CI systems talk with Apache
> Infra?
> > >
> > > I ask be
th Apache
Infra?
> >
> > I ask because I've spend around a day now trying to convince Travis CI
to build log4net successfully, without a lot of joy, particularly because
the Travis Windows build environment is quite out of date, having been
launched as a beta service in 2018, with t
ra.apache.org/services.html
> >> >
> >> > If nothing on there is appropriate, I think we need to create a Jira
> >> > ticket in https://issues.apache.org/jira/browse/INFRA
> >> >
> >> > On Mon, 27 Apr 2020 at 01:28, Davyd McColl wrote:
>
Mileage may vary, but I see no point in supporting ancient frameworks.
Better support only few valuable targets well and offload maintenance
efforts to whoever needs other targets that are hard to support. For
instance, whoever builds against client profile could fork and build
log4net from source
valuable targets well and offload maintenance
efforts to whoever needs other targets that are hard to support. For
instance, whoever builds against client profile could fork and build
log4net from source. Patches to make it work are valuable and always
welcome, now and anytime in the future. Those pa
ort only few valuable targets well and offload maintenance
> > efforts to whoever needs other targets that are hard to support. For
> > instance, whoever builds against client profile could fork and build
> > log4net from source. Patches to make it work are valuable and always
&g
no point in supporting ancient frameworks.
> > > Better support only few valuable targets well and offload maintenance
> > > efforts to whoever needs other targets that are hard to support. For
> > > instance, whoever builds against client profile could fork and build
>
gt;
> -d
>
>
> On April 27, 2020 21:44:29 Dominik Psenner wrote:
>
> > Mileage may vary, but I see no point in supporting ancient frameworks.
> > Better support only few valuable targets well and offload maintenance
> > efforts to whoever needs other targets that are hard to
t; >> >
> >> > On April 27, 2020 21:44:29 Dominik Psenner wrote:
> >> >
> >> > > Mileage may vary, but I see no point in supporting ancient frameworks.
> >> > > Better support only few valuable targets well and offload maintenance
> >
Hi,
Do we have any further update on this, any plan for releasing 2.1.0
Thanks,
Satish
On 2020/04/04 22:24:59, Ralph Goers wrote:
> I have modified the STATUS.txt and README.txt for Log4Net, tagged the source,
> zipped it and then published it to
> https://dist.apache.org/repos
Dear Team,
Can you please provide an update on the below query. This is about the 2.1.0
release for issue LOG4NET-575.
Currently we have a XXE vulnerability raised for log4net in our application.
Our application uses log4net version 2.0.8 and Microsoft .net framework 4.5.2.
By default, .net
involved and drive forward a release of binaries along
others who have chimed in.
Option 2 is to consume log4net sources, building a head revision that
includes the fix.
Option 3 is to fork and do what You see fit and is allowed according to the
license agreement.
Best Regards,
Dominik
--
Sent
1 is to get involved and drive forward a release of binaries along
> others who have chimed in.
>
> Option 2 is to consume log4net sources, building a head revision that
> includes the fix.
>
> Option 3 is to fork and do what You see fit and is allowed according to the
> license
the
> > project. I see at least these options:
> >
> > Option 1 is to get involved and drive forward a release of binaries along
> > others who have chimed in.
> >
> > Option 2 is to consume log4net sources, building a head revision that
> > includes t
roposed vote to release log4net 2.0.9 from PR
https://github.com/apache/logging-log4net/pull/61
Release artifacts (including source zip) are at:
https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063235/artifacts
Source can be checked out from
https://github.com/fluffynuts/logging-
ion around sender address -- I've already
> fluffed this by sending from my work account (default in my mail client)
>
> -d
>
> On 2020/07/31 08:26:54, Davyd McColl wrote:
> Hi all, I've never done this before, so bear with me if I fluff it:
>
> This is a proposed
unt (default in my mail client)
-d
On 2020/07/31 08:26:54, Davyd McColl wrote:
Hi all, I've never done this before, so bear with me if I fluff it:
This is a proposed vote to release log4net 2.0.9 from PR
https://github.com/apache/logging-log4net/pull/61
Release artifacts (including so
> >>
> >> Apologies if there's any confusion around sender address -- I've already
> >> fluffed this by sending from my work account (default in my mail client)
> >>
> >> -d
> >>
> >> On 2020/07/31 08:26:54, Davyd McColl wrote:
> &g
gt;
>> -d
>>
>> On 2020/07/31 08:26:54, Davyd McColl wrote:
>> Hi all, I've never done this before, so bear with me if I fluff it:
>>
>> This is a proposed vote to release log4net 2.0.9 from PR
>> https://github.com/apache/logging-log4net/pull/61
Can other PMC members please review this? It has been more than 72 hours.
Ralph
> On Jul 30, 2020, at 11:17 PM, Davyd McColl wrote:
>
> Hi all, I've never done this before, so bear with me if I fluff it:
>
> This is a proposed vote to release log4net 2.0.9 from PR
>
> > Hi all, I've never done this before, so bear with me if I fluff it:
> >
> > This is a proposed vote to release log4net 2.0.9 from PR
> > https://github.com/apache/logging-log4net/pull/61
> >
> > Release artifacts (including source zip) are at:
&
2
> hours.
> >
> > Ralph
> >
> > > On Jul 30, 2020, at 11:17 PM, Davyd McColl
> wrote:
> > >
> > > Hi all, I've never done this before, so bear with me if I fluff it:
> > >
> > > This is a proposed vote to release log4n
e:
>>>>
>>>> Hi all, I've never done this before, so bear with me if I fluff it:
>>>>
>>>> This is a proposed vote to release log4net 2.0.9 from PR
>> https://github.com/apache/logging-log4net/pull/61
>>>>
>>>>
please review this? It has been more than 72
> >> hours.
> >>>
> >>> Ralph
> >>>
> >>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
> >> wrote:
> >>>>
> >>>> Hi all, I've never done this before
ph
> > >> suggests.
> > >>
> > >> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
> > >> wrote:
> > >>>
> > >>> Can other PMC members please review this? It has been more than 72
> > >> hours.
> > >>>
&g
Just a simple copy of the LICENSE and NOTICE file into the binaries
zip, and a rename of the files to include "apache" in the name. I've
uploaded them to dist along with updating the KEYS file for log4net,
though that should probably be merged together with the project-wide
KEYS fil
ve
> > uploaded them to dist along with updating the KEYS file for log4net,
> > though that should probably be merged together with the project-wide
> > KEYS file in the parent directory. There's an outdated README.html in
> > the directory still containing the old release
copy of the LICENSE and NOTICE file into the binaries
zip, and a rename of the files to include "apache" in the name. I've
uploaded them to dist along with updating the KEYS file for log4net,
though that should probably be merged together with the project-wide
KEYS file in the paren
gt;>
>>
>> On August 16, 2020 20:37:01 Matt Sicker wrote:
>>
>>> Just a simple copy of the LICENSE and NOTICE file into the binaries
>>> zip, and a rename of the files to include "apache" in the name. I've
>>> uploaded them to dist along with
I committed them to dist already. I don't know how long we should wait
for any mirroring to catch up, though on my end, I see updated
artifacts on https://downloads.apache.org/logging/log4net/ other than
the release notes.
On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>
> +1 to th
wait
for any mirroring to catch up, though on my end, I see updated
artifacts on https://downloads.apache.org/logging/log4net/ other than
the release notes.
On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>
> +1 to that!
>
> Let me know when these are published. I can update the web si
e
> useful? Or is there a better way?
>
> -d
> On 2020/08/16 23:26:07, Matt Sicker wrote:
> I committed them to dist already. I don't know how long we should wait
> for any mirroring to catch up, though on my end, I see updated
> artifacts on https://downloads.apache.or
l? Or is there a better way?
-d
On 2020/08/16 23:26:07, Matt Sicker wrote:
I committed them to dist already. I don't know how long we should wait
for any mirroring to catch up, though on my end, I see updated
artifacts on https://downloads.apache.org/logging/log4net/ other than
the release
s there a better way?
>
> -d
> On 2020/08/16 23:26:07, Matt Sicker wrote:
> I committed them to dist already. I don't know how long we should wait
> for any mirroring to catch up, though on my end, I see updated
> artifacts on https://downloads.apache.org/logging/log4net/ othe
a
CHANGELOG file be useful? Or is there a better way?
-d
On 2020/08/16 23:26:07, Matt Sicker wrote:
I committed them to dist already. I don't know how long we should wait
for any mirroring to catch up, though on my end, I see updated
artifacts on https://downloads.apache.org/logging/log4net
if I were to try to streamline that into a release, would
> a
> >> CHANGELOG file be useful? Or is there a better way?
> >>
> >> -d
> >> On 2020/08/16 23:26:07, Matt Sicker wrote:
> >> I committed them to dist already. I don't know how long we
Notes area -- if I were to try to streamline that into a release, would
a
>> CHANGELOG file be useful? Or is there a better way?
>>
>> -d
>> On 2020/08/16 23:26:07, Matt Sicker wrote:
>> I committed them to dist already. I don't know how long we should w
you posted, I have ideas on how to
>>> >> streamline future releases, so the next time I'm in that area, I'm
>>> >> definitely implementing those ideas. I don't see changes to the Release
>>> >> Notes area -- if I were to try to streamline
tes area -- if I were to try to streamline that into a release, would a
>> CHANGELOG file be useful? Or is there a better way?
>>
>> -d
>> On 2020/08/16 23:26:07, Matt Sicker wrote:
>> I committed them to dist already. I don't know how long we should wait
there a better way?
>>>
>>> -d
>>> On 2020/08/16 23:26:07, Matt Sicker wrote:
>>> I committed them to dist already. I don't know how long we should wait
>>> for any mirroring to catch up, though on my end, I see updated
>>> artifacts on https://downloa
#x27;s at the url you posted, I have ideas on how to
>>>> streamline future releases, so the next time I'm in that area, I'm
>>>> definitely implementing those ideas. I don't see changes to the Release
>>>> Notes area -- if I were to try to strea
>>> streamline future releases, so the next time I'm in that area, I'm
>>>>> definitely implementing those ideas. I don't see changes to the Release
>>>>> Notes area -- if I were to try to streamline that into a release, would a
>>
going to be interested in.
>>>>>>
>>>>>> Having a look at what's at the url you posted, I have ideas on how to
>>>>>> streamline future releases, so the next time I'm in that area, I'm
>>>>>> definitely implementing th
gt;>>>>> How do we get the nupkg to nuget.org? This is the final step that
> most
> >>>>>> users are going to be interested in.
> >>>>>>
> >>>>>> Having a look at what's at the url you posted, I have ideas on how
&
ng to be interested in.
>>>>>>
>>>>>> Having a look at what's at the url you posted, I have ideas on how
to
>>>>>> streamline future releases, so the next time I'm in that area, I'm
>>>>>> definitely implementing th
ecipients
> with
> >> their
> >> >>>>> gpg key.
> >> >>>>> --
> >> >>>>> Sent from my phone. Typos are a kind gift to anyone who happens to
> >> find
> >> >>>>> them.
> >> >&
;> >>>>> Sent from my phone. Typos are a kind gift to anyone who happens to
>> find
>> >>>>> them.
>> >>>>>
>> >>>>> On Mon, Aug 17, 2020, 08:56 Davyd McColl
wrote:
>> >>>>>
>> >>>
n Aug 17, 2020, at 9:39 AM, Dominik Psenner <
> dpsen...@gmail.com>
> >> >> wrote:
> >> >> >>>>>
> >> >> >>>>> I guess that would be a nuget publish.
> >> >> >>>>>
> &g
Thanks Dominik
Are there any objections to me pushing the 2.0.9 package that had been
approved and uploaded to https://downloads.apache.org/logging/log4net/ to
nuget.org?
-d
On August 23, 2020 09:59:02 Dominik Psenner wrote:
Davyd, I added you as a collaborator. This should grant you
There can’t be. That is what the release vote was for.
Ralph
> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
>
> Thanks Dominik
>
> Are there any objections to me pushing the 2.0.9 package that had been
> approved and uploaded to https://downloads.apache.org/l
t; >
> > Thanks Dominik
> >
> > Are there any objections to me pushing the 2.0.9 package that had been
> > approved and uploaded to https://downloads.apache.org/logging/log4net/ to
> > nuget.org?
> >
> > -d
> >
> >
> >> On August 23,
Ok, log4net 2.0.9 is up on nuget.org (:
Thanks for all the help (:
-d
On 2020/08/23 19:13:36, Matt Sicker wrote:
Yes, please go ahead and finish the release. The PMC approved this
during our release vote. :)
On Sun, 23 Aug 2020 at 10:22, Apache wrote:
>
> There can’t be. That is wh
Thanks again for managing the release! I’m sure you’ve just made a lot of
developers happy. :D
On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
> Ok, log4net 2.0.9 is up on nuget.org (:
>
>
>
> Thanks for all the help (:
>
>
>
> -d
>
>
>
> On 2020/08/2
Hi
People noticed that the release notes of 2.0.9 are missing while they
should be documented here:
http://logging.apache.org/log4net/release/release-notes.html
Best regards
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
Well done, everyone!
On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
> Thanks again for managing the release! I’m sure you’ve just made a lot of
> developers happy. :D
>
> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>
> > Ok, log4net 2.0.9 is up on nuget.org (:
&
gt;> Thanks again for managing the release! I’m sure you’ve just made a lot of
>> developers happy. :D
>>
>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>>
>>> Ok, log4net 2.0.9 is up on nuget.org (:
>>>
>>>
>>>
>>> Tha
ust made a lot of
>>> developers happy. :D
>>>
>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>>>
>>>> Ok, log4net 2.0.9 is up on nuget.org (:
>>>>
>>>>
>>>>
>>>> Thanks for all the help (:
>
yone!
>>
>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
>>
>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
>>> developers happy. :D
>>>
>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>>>
>>
gt;> Ralph
>>
>>>> On Aug 24, 2020, at 2:45 PM, Remko Popma wrote:
>>>
>>> Well done, everyone!
>>>
>>>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
>>>
>>>> Thanks again for managing the
2:45 PM, Remko Popma wrote:
>>>
>>> Well done, everyone!
>>>
>>>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
>>>
>>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
>>>> developers happy. :
dated.
> >>
> >> Ralph
> >>
> >>>> On Aug 24, 2020, at 2:45 PM, Remko Popma wrote:
> >>>
> >>> Well done, everyone!
> >>>
> >>>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
> >>&g
201 - 300 of 1120 matches
Mail list logo
