Hi
asf-staging branch merged into asf-site and I can see the latest release notes
are up
Apologies again for missing this.
-d
On 2021/11/05 16:31:41, Davyd McColl wrote:
Apologies - staging docs have not been set live ):
I'll have a look at it now
-d
On 2021/11/05 16:24:55, Volkan Yazıcı
Apologies - staging docs have not been set live ):
I'll have a look at it now
-d
On 2021/11/05 16:24:55, Volkan Yazıcı wrote:
I think this message is best suited for this mailing list.
Would anybody from the log4net crew mind addressing the request of John
Bigler, please?
-- Forwarded
I think this message is best suited for this mailing list.
Would anybody from the log4net crew mind addressing the request of John
Bigler, please?
-- Forwarded message -
From: NuGet Gallery
Date: Thu, Nov 4, 2021 at 5:50 PM
Subject: [NuGet Gallery] Message for owners of the
Dear Santosh,
please see the answer to Your request below. Please note that Apache
product discussions happen on mailing lists, in this case it is
dev@logging.apache.org. NuGet messages are not an ideal way to communicate
because they reach only a limited subset of the community.
Warm regards,
Hi Dominik
iirc, this was fixed in 2.0.11. 2.0.12, with another fix for current user
name on !win32, is waiting on one more +1 vote for release.
-d
On October 23, 2020 18:05:18 Dominik Psenner wrote:
See the message below.
--
Sent from my phone.
-- Forwarded message -
See the message below.
--
Sent from my phone.
-- Forwarded message -
From: NuGet Gallery
Date: Fri, Oct 23, 2020, 07:51
Subject: [NuGet Gallery] Message for owners of the package 'log4net'
To:
*User santoshkallatti > sends the following message to
the owners of Package
Ok, I've found the culprit -- there's a lot of assembly version sources which
mention 2.0.9 -- and I'm not entirely sure why some of them are in this project
(AssemblyVersionInfo.cpp, AssemblyVersionInfo.js, AssemblyVersionInfo.vb). And
there are two files which set up assembly version
hm, that's not great ): I'll investigate. Thanks for letting me know!
-d
On 2020/09/18 13:05:58, Dominik Psenner wrote:
See the message below. Apparently something went wrong during the last
release.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
--
See the message below. Apparently something went wrong during the last
release.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
-- Forwarded message -
From: NuGet Gallery
Date: Fri, Sep 18, 2020, 12:10
Subject: [NuGet Gallery] Message for owners
This reflects my impression that the volume of individuals that do not know
the mechanics of the mailing lists has increased. I observe that with the
increased number of messages that need to be moderated. Many come from
individuals that are not subscribes. Others come from individuals that send
True that, but I tried to initiate a vote the other day from my work mail
by mistake and the message was bounced, so I'm not sure what rules apply to
this list. If it's fairly open, it might be a plan to update the associated
email address on nuget to the dev list.
-d
On September 8, 2020
That's this dev list! Though if we need a separate mailing list, we
can always create more.
On Tue, 8 Sep 2020 at 11:54, Davyd McColl wrote:
>
> What if there was another Apache email address that messages were sent to,
> and multiple people could observe that account? I don't mind being one of
What if there was another Apache email address that messages were sent to,
and multiple people could observe that account? I don't mind being one of
the lucky ones if it will help (:
-d
On September 8, 2020 17:47:57 Matt Sicker wrote:
The main problem with sending nuget info to the PMC is
The main problem with sending nuget info to the PMC is that nobody in
the PMC are working on log4net besides validating releases ;)
On Tue, 8 Sep 2020 at 04:37, Dominik Psenner wrote:
>
> In the past security vulnerabilities were reported via nuget and it is not
> a good idea to publish those in
In the past security vulnerabilities were reported via nuget and it is not
a good idea to publish those in an automated way.
I suggest to update the nuget project documentation and prominently point
to our mailing lists and discourage the communication via nuget. Users may
continue sending
Ralph
I understand that the emails provide a bit of workload, and I'm trying to
figure out a solution to help everyone -- obviously there are people who submit
mails (and wonder where they went) and people who have to handle those mails.
We use Trello at work and have built our own custom
Hi Ralph
I'll investigate this today. I'd like more information, particularly
configuration and, eg if the ado.net appender is used, table structures.
Joseph, please open a ticket at
https://issues.apache.org/jira/browse/LOG4NET to help me track this.
-d
On September 7, 2020 23:35:12
For some reason all messages from NuGet are routed to the Apache Logging PMC
list. This one clearly does not need to be private. Just know that the person
who sent this is apparently not subscribed to the ASF mailing lists so won’t
see a response unless he is cc’d.
I’m not familiar with NuGet
On 2018-07-19 22:17, sean.co...@gmail.com wrote:
Dominik,
There are a number of issues in your tracker that are directly related to
sticking with NetStandard 1.3. That was an early release and must have been
painful to try to do a full implementation of Log4Net. 2 issues dear to me are
Dominik,
There are a number of issues in your tracker that are directly related to
sticking with NetStandard 1.3. That was an early release and must have been
painful to try to do a full implementation of Log4Net. 2 issues dear to me are
Variable Expansion (Environment.GetEnvironmentVariable
Hi Bart,
thanks for your interest in log4net. There's an issue for this and we
have an open pull request that adds this target. We have however no plan
yet of when this should happen. By targeting log4net against
netstandard-1.3 it can be referenced from that netstandard and any
netstandard
21 matches
Mail list logo
