[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varlamov Oleg updated LOG4NET-558:
--
Description:
When we are updated log4net from 1.2.15 to 2.0.7 some of our customers report
abo
[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varlamov Oleg updated LOG4NET-558:
--
Affects Version/s: 2.0.8
> log4net 2.0.7 and greater doesn't log %message pattern
> ---
[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varlamov Oleg updated LOG4NET-558:
--
Affects Version/s: (was: 2.0.8)
> log4net 2.0.7 and greater doesn't log %message pattern
>
[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varlamov Oleg updated LOG4NET-558:
--
Description:
When we are updated log4net from 1.2.15 to 2.0.7 some of our customers report
abo
[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varlamov Oleg updated LOG4NET-558:
--
Description:
When we are updated log4net from 1.2.15 to 2.0.7 some of our customers report
abo
[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varlamov Oleg updated LOG4NET-558:
--
Description:
When we are updated log4net from 1.2.15 to 2.0.7 some of our customers report
abo
[
https://issues.apache.org/jira/browse/LOG4NET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varlamov Oleg updated LOG4NET-558:
--
Description:
When we are updated log4net from 1.2.15 to 2.0.7 some of our customers report
abo
Varlamov Oleg created LOG4NET-558:
-
Summary: log4net 2.0.7 and greater doesn't log %message pattern
Key: LOG4NET-558
URL: https://issues.apache.org/jira/browse/LOG4NET-558
Project: Log4net
Is
1. That seems fine to me.
2. Is it possible to do both? I like the idea of annoying the sender but still
allowing the email to be sent. It would cool if it could even add [list] to the
start of the subject line.
3. This is the main thing that needs to happen.
Ralph
> On Mar 12, 2017, at 7:49
Some things:
1. Archives won't be merged.
2. Infra suggests it might be a better idea to have the old email addresses
respond with a canned reply saying that the lists have moved over to dev@,
though they can set it up all as aliases if we prefer.
3. Current subscribers from all dev lists would be
Created a request, not sure if it's public:
https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13651
On 12 March 2017 at 17:11, Ralph Goers wrote:
> Yes,
>
> If you could send the request to infra I would appreciate it.
>
> Ralph
>
> On Mar 12, 2017, at 1:13 PM, Matt Sicker wrot
Yes,
If you could send the request to infra I would appreciate it.
Ralph
> On Mar 12, 2017, at 1:13 PM, Matt Sicker wrote:
>
> The vote has been open for 5 days now. Based on the tallies and discussions,
> it sounds like we'd like to merge the dev lists but keep the user lists as
> is. Shall
The vote has been open for 5 days now. Based on the tallies and
discussions, it sounds like we'd like to merge the dev lists but keep the
user lists as is. Shall we move forward with combining them now?
On 10 March 2017 at 12:27, Dominik Psenner wrote:
> Total agreement.
>
> On 10 Mar 2017 6:26
13 matches
Mail list logo
