that
> > worked the release notes would look terrible.
> >
> > Ralph.
> >
> > > On Dec 8, 2021, at 5:23 AM, Gary Gregory
> wrote:
> > >
> > > If you refer to
> > >
> https://logging.staged.apache.org/log4j/2.x/changes-report.html#a2.15.0
> > I'm
orked the release notes would look terrible.
>
> Ralph.
>
> > On Dec 8, 2021, at 5:23 AM, Gary Gregory wrote:
> >
> > If you refer to
> > https://logging.staged.apache.org/log4j/2.x/changes-report.html#a2.15.0
> I'm
> > not sure what we can do unless ther
ot sure what we can do unless there is special sauce to use in
> changes.xml. Are we supposed to use HTML in a changes.xml entry? That would
> be simple enough.
>
> Gary
>
>> On Tue, Dec 7, 2021 at 5:05 PM Ralph Goers
>> wrote:
>>
>> Gary,
>>
>> P
If you refer to
https://logging.staged.apache.org/log4j/2.x/changes-report.html#a2.15.0 I'm
not sure what we can do unless there is special sauce to use in
changes.xml. Are we supposed to use HTML in a changes.xml entry? That would
be simple enough.
Gary
On Tue, Dec 7, 2021 at 5:05 PM Ralph
Gary,
Please review the manual changes for 2.15.0 on the staging web site. The last
item is yours from
upgrading a bunch of dependency versions.
I spent a bunch of time yesterday trying to figure out how to make that pretty
and finally gave up.
It requires knowing now the changes plugin
I have copied the 2.14.1 of changes.xml from release-2.x to master and I
have removed the duplicates in the 3.0.0. Note that the 3.0.0 block in
master still needs to be grouped into fixes, updates, etc. sections. I will
do that grouping if you are okay with the previous change.
On Fri, Mar 5
; Are you gonna tidy it up or shall I give it a try?
>
>
> On Fri, Mar 5, 2021 at 7:23 AM Ralph Goers
> wrote:
>
>> Looking at changes.xml it looks like actions that are being fixed in
>> 2.14.1 in the release-2.x branch and 3.0.0 in master. This will create
>>
臘♂️ I am in that group of people.
Thanks for the warning and sorry for the mess.
Are you gonna tidy it up or shall I give it a try?
On Fri, Mar 5, 2021 at 7:23 AM Ralph Goers
wrote:
> Looking at changes.xml it looks like actions that are being fixed in
> 2.14.1 in the release-2.x
Looking at changes.xml it looks like actions that are being fixed in 2.14.1 in
the release-2.x branch and 3.0.0 in master. This will create confusion for
users when 3.0.0 is released as we will be listing a pile of fixes that were
actually fixed in prior releases.
Please add the actions
>> Talph,
>>
>> Feel free to edit changes.xml as you best see fit.
>>
>> Gary
>>
>> On Tue, Aug 13, 2019, 22:37 Ralph Goers
>> wrote:
>>
>>> The “By” column is a link to the team list that includes all your
>>> i
Just don’t remove any due-to changes from committers from before they
became committers.
On Wed, Aug 14, 2019 at 00:42, Gary Gregory wrote:
> Talph,
>
> Feel free to edit changes.xml as you best see fit.
>
> Gary
>
> On Tue, Aug 13, 2019, 22:37 Ralph Goers
> wrot
Talph,
Feel free to edit changes.xml as you best see fit.
Gary
On Tue, Aug 13, 2019, 22:37 Ralph Goers wrote:
> The “By” column is a link to the team list that includes all your
> information. If you don’t use your userid then the link won’t index into
> the list properly.
&g
>
>> Ralph
>>
>>> On Aug 13, 2019, at 8:13 PM, Ralph Goers
>> wrote:
>>>
>>> Gary,
>>>
>>> I am wondering why you have recently gotten in the habit of adding
>> yourself to the due-to field of changes.xml. Historically we hav
9, 20:13 Ralph Goers wrote:
>>
>> Gary,
>>
>> I am wondering why you have recently gotten in the habit of adding
>> yourself to the due-to field of changes.xml. Historically we have always
>> used that to give credit to non-committers who provide patches or
&g
due-to field of changes.xml. Historically we have always
> used that to give credit to non-committers who provide patches or
> significantly contribute to them. As committers we get credit in the
> source control and in the dev field of the action entry. It seems over the
> top to be
m wondering why you have recently gotten in the habit of adding
> yourself to the due-to field of changes.xml. Historically we have always
> used that to give credit to non-committers who provide patches or
> significantly contribute to them. As committers we get credit in the
> sourc
giving yourself credit twice.
Ralph
> On Aug 13, 2019, at 8:13 PM, Ralph Goers wrote:
>
> Gary,
>
> I am wondering why you have recently gotten in the habit of adding yourself
> to the due-to field of changes.xml. Historically we have always used that to
> give credit to
Gary,
I am wondering why you have recently gotten in the habit of adding yourself to
the due-to field of changes.xml. Historically we have always used that to give
credit to non-committers who provide patches or significantly contribute to
them. As committers we get credit in the source
ething
> introduced in 3.0. Changes.xml should reflect the version the fix or feature
> was first added.
>
> Please remove the duplicates from 3.0.
>
> Ralph
>
> > On Jun 3, 2019, at 4:14 AM, Gary Gregory wrote:
> >
> > Are you sure? The reason I d
Am I sure about what? Who cares when the branches diverged? If a fix or feature
was introduced prior to 3.0 then it shouldn’t be listed as something introduced
in 3.0. Changes.xml should reflect the version the fix or feature was first
added.
Please remove the duplicates from 3.0.
Ralph
Are you sure? The reason I did it like this is to track changes from when
the branches diverged.
Gary
On Sun, Jun 2, 2019 at 5:45 PM Ralph Goers
wrote:
> Gary,
>
> In looking at the changes.xml in 3.0 it looks like you are adding
> notations to both the 2.x and 3.x releases. That
Gary,
In looking at the changes.xml in 3.0 it looks like you are adding notations to
both the 2.x and 3.x releases. That doesn’t make any sense. A change should be
noted ONLY in the release in which it was first published. Can you please go
through all the actions you added to the 3.0 release
The JIRA tickets themselves are still marked as Fixed Version 2.11, Gary,
would you mind updating them?
On Thu, Feb 1, 2018 at 9:09 PM, <rpo...@apache.org> wrote:
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master 041fe8ffe -> a9e8f525a
>
>
> Upd
Hi All:
Just FYI: The file changes.xml states 2.11.0 but POMs state 2.10.1
Gary
> Gary
>
> -- Forwarded message --
> From: <ma...@apache.org>
> Date: Thu, Nov 3, 2016 at 4:44 AM
> Subject: svn commit: r1767873 - in /commons/proper/daemon/trunk: build.xml
> pom.xml src/changes/changes.xml
> To: comm...@commons.apache.org
>
>
> Author
svn commit: r1767873 - in /commons/proper/daemon/trunk: build.xml
> pom.xml src/changes/changes.xml
> To: comm...@commons.apache.org
>
>
> Author: markt
> Date: Thu Nov 3 11:44:02 2016
> New Revision: 1767873
>
> URL: http://svn.apache.org/viewvc?rev=176787
Why not Java 7?
Gary
-- Forwarded message --
From: <ma...@apache.org>
Date: Thu, Nov 3, 2016 at 4:44 AM
Subject: svn commit: r1767873 - in /commons/proper/daemon/trunk: build.xml
pom.xml src/changes/changes.xml
To: comm...@commons.apache.org
Author: markt
Date: Thu Nov 3
Author: tschoening
Date: Sun Oct 23 13:27:30 2016
New Revision: 1766278
URL: http://svn.apache.org/viewvc?rev=1766278=rev
Log:
LOGCXX-484: Spelling error s/excute/execute
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp/odbcappender.cpp
On Sun, Aug 28, 2016 at 12:00 PM, Ralph Goers <ralph.go...@dslextreme.com>
wrote:
> The changes.xml already says 2.7. The versions in the poms don’t matter.
> I know I have told you this before, but no matter what you set them to the
> release plugin is going to change them to wha
The changes.xml already says 2.7. The versions in the poms don’t matter. I
know I have told you this before, but no matter what you set them to the
release plugin is going to change them to whatever version I set when I run the
release build. So modifying the pom versions now is just a waste
reme.com>
>>> wrote:
>>>
>>>> I’m sure I have stuff I want to do. It just isn’t going to get done
>>>> this week. The soonest I could target doing a release would be labor day
>>>> weekend. But I expect I will probably spend most of that ad
gory <garydgreg...@gmail.com> wrote:
>
>> Sounds like a clean up is needed. I can take care of my due-to's.
>>
>> Gary
>>
>> On Fri, Aug 26, 2016 at 7:28 PM, Matt Sicker <boa...@gmail.com> wrote:
>>
>>> That makes sense. Should we clean up
That makes sense. Should we clean up changes.xml then?
>>
>> On 26 August 2016 at 18:41, Ralph Goers <ralph.go...@dslextreme.com>
>> wrote:
>>
>>> One other thing. I also review the due-to’s in changes.xml to look for
>>> potential committers. Having people w
> wrote:
>
>> That makes sense. Should we clean up changes.xml then?
>>
>> On 26 August 2016 at 18:41, Ralph Goers <ralph.go...@dslextreme.com>
>> wrote:
>>
>>> One other thing. I also review the due-to’s in changes.xml to look for
>>> p
Sounds like a clean up is needed. I can take care of my due-to's.
Gary
On Fri, Aug 26, 2016 at 7:28 PM, Matt Sicker <boa...@gmail.com> wrote:
> That makes sense. Should we clean up changes.xml then?
>
> On 26 August 2016 at 18:41, Ralph Goers <ralph.go...@dslextreme.com>
&g
That makes sense. Should we clean up changes.xml then?
On 26 August 2016 at 18:41, Ralph Goers <ralph.go...@dslextreme.com> wrote:
> One other thing. I also review the due-to’s in changes.xml to look for
> potential committers. Having people who are already committers there ju
One other thing. I also review the due-to’s in changes.xml to look for
potential committers. Having people who are already committers there just
muddies the waters.
So as a general rule I would ask that committers refrain from listing
themselves on the due-to attribute.
Ralph
> On Aug
really matter. It's more useful in
> larger projects where you have a hierarchy of project leaders involved.
>
> Should we sign commits?
>
> Gary
>
>
> On 26 August 2016 at 18:02, Gary Gregory <garydgreg...@gmail.com
> <mailto:garydgreg...@gmail.com>> wrot
hierarchy of project leaders involved.
>
>> On 26 August 2016 at 18:02, Gary Gregory <garydgreg...@gmail.com> wrote:
>> Are you suggesting we augment the changes.xml model to reflect the 3rd attr?
>>
>> G
>>
>>> On Fri, Aug 26, 2016 at 4:
;>
>> On 26 August 2016 at 18:02, Gary Gregory <garydgreg...@gmail.com> wrote:
>>
>>> Are you suggesting we augment the changes.xml model to reflect the 3rd
>>> attr?
>>>
>>> G
>>>
>>> On Fri, Aug 26, 2016 at 4:02 PM, Matt S
t 2016 at 18:02, Gary Gregory <garydgreg...@gmail.com> wrote:
>
>> Are you suggesting we augment the changes.xml model to reflect the 3rd
>> attr?
>>
>> G
>>
>> On Fri, Aug 26, 2016 at 4:02 PM, Matt Sicker <boa...@gmail.com> wrote:
>>
>
We don't gpg-sign commits, so it wouldn't really matter. It's more useful
in larger projects where you have a hierarchy of project leaders involved.
On 26 August 2016 at 18:02, Gary Gregory <garydgreg...@gmail.com> wrote:
> Are you suggesting we augment the changes.xml model to reflec
Are you suggesting we augment the changes.xml model to reflect the 3rd attr?
G
On Fri, Aug 26, 2016 at 4:02 PM, Matt Sicker <boa...@gmail.com> wrote:
> Git has 3 distinctions though: author, committer, and signed off by (which
> is optional).
>
> On 26 August 2016 at 1
ry <garydgreg...@gmail.com> wrote:
>>
>>> Copy-paste. Would you rather it does not show up with a due-to?
>>>
>>> Gary
>>>
>>> On Fri, Aug 26, 2016 at 3:05 PM, Ralph Goers <ralph.go...@dslextreme.com
>>> > wrote:
>>>
>&g
e.com>
>> wrote:
>>
>>> Gary,
>>>
>>> I am noticing that you have marked several items in changes.xml as
>>> “due-to” yourself? Why are you doing that? Traditionally, we have omitted
&
Ralph Goers <ralph.go...@dslextreme.com>
> wrote:
>
>> Gary,
>>
>> I am noticing that you have marked several items in changes.xml as
>> “due-to” yourself? Why are you doing that? Traditionally, we have omitted
>> that when a committer does the work as it
Copy-paste. Would you rather it does not show up with a due-to?
Gary
On Fri, Aug 26, 2016 at 3:05 PM, Ralph Goers <ralph.go...@dslextreme.com>
wrote:
> Gary,
>
> I am noticing that you have marked several items in changes.xml as
> “due-to” yourself? Why are you doing that?
Gary,
I am noticing that you have marked several items in changes.xml as “due-to”
yourself? Why are you doing that? Traditionally, we have omitted that when a
committer does the work as it shows up as you making the commit in the report.
Ralph
doing a release would be labor day
>>> weekend. But I expect I will probably spend most of that addressing issues
>>> I’ve been trying to get to.
>>>
>>> Ralph
>>>
>>> On Aug 22, 2016, at 5:32 PM, Gary Gregory <garydgreg...@gmail.com>
>
;>> wrote:
>>>
>>>> I’m sure I have stuff I want to do. It just isn’t going to get done
>>>> this week. The soonest I could target doing a release would be labor day
>>>> weekend. But I expect I will probably spend most of that addressing issues
&g
elease would be labor day
>>> weekend. But I expect I will probably spend most of that addressing issues
>>> I’ve been trying to get to.
>>>
>>> Ralph
>>>
>>> On Aug 22, 2016, at 5:32 PM, Gary Gregory <garydgreg...@gmail.com>
>>
>> I’m sure I have stuff I want to do. It just isn’t going to get done this
>> week. The soonest I could target doing a release would be labor day weekend.
>> But I expect I will probably spend most of that addressing issues I’ve been
>> trying to get to.
>>
>> Ralph
&g
target doing a release would be labor day
>>> weekend. But I expect I will probably spend most of that addressing issues
>>> I’ve been trying to get to.
>>>
>>> Ralph
>>>
>>>> On Aug 22, 2016, at 5:32 PM, Gary Gregory <garydgreg...@gmai
get to.
>>>
>>> Ralph
>>>
>>> On Aug 22, 2016, at 5:32 PM, Gary Gregory <garydgreg...@gmail.com>
>>> wrote:
>>>
>>> Wow, we've already accumulated 35 items in changes.xml since release
>>> 2.6.2 on July 5!
>>>
>&g
om> wrote:
>
> Wow, we've already accumulated 35 items in changes.xml since release 2.6.2
> on July 5!
>
> I'm not sure if that is good or bad ;-) but we should think about what we
> want to complete for the next release.
>
> Thoughts?
>
> Gary
>
> --
> E-Mail: gar
ory <garydgreg...@gmail.com> wrote:
>
> Wow, we've already accumulated 35 items in changes.xml since release 2.6.2 on
> July 5!
>
> I'm not sure if that is good or bad ;-) but we should think about what we
> want to complete for the next release.
>
> Thou
Wow, we've already accumulated 35 items in changes.xml since release 2.6.2
on July 5!
I'm not sure if that is good or bad ;-) but we should think about what we
want to complete for the next release.
Thoughts?
Gary
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence
mentione din LOGCXX-400.
http://stackoverflow.com/questions/28094263/create-array-of-chars-avoiding-narrowing?rq=1#comment44564938_28094263
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp/locationinfo.cpp
incubator/log4cxx/trunk/src/main/cpp
Author: tschoening
Date: Sun Apr 10 10:37:05 2016
New Revision: 1738416
URL: http://svn.apache.org/viewvc?rev=1738416=rev
Log:
LOGCXX-464: TimeBasedRollingPolicy should append as configured on rollover
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx
Author: tschoening
Date: Thu Mar 24 11:42:36 2016
New Revision: 1736429
URL: http://svn.apache.org/viewvc?rev=1736429=rev
Log:
LOGCXX-433: Autoconf 2.69 needs 'ACLOCAL_AMFLAGS= -I .'
Modified:
incubator/log4cxx/trunk/Makefile.am
incubator/log4cxx/trunk/src/changes/changes.xml
Modified
Author: tschoening
Date: Thu Mar 24 10:53:11 2016
New Revision: 1736418
URL: http://svn.apache.org/viewvc?rev=1736418=rev
Log:
LOGCXX-400 was fixed
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL:
http://svn.apache.org
Author: rhys
Date: Tue Oct 21 12:07:24 2014
New Revision: 1633356
URL: http://svn.apache.org/r1633356
Log:
LOG4CXX-443: Return by const reference in Logger::getName()
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/include/log4cxx/logger.h
changed the problem of not beeing
thread safe with another one and I was surely only lucky in my former runs of
the testsuite to succeed. Currently they don't, so I'll revert my changes and
reopen the issue again.
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx
Original message /divdivFrom: mattsic...@apache.org
/divdivDate:08/16/2014 23:25 (GMT-05:00) /divdivTo:
comm...@logging.apache.org /divdivSubject: svn commit: r1618449 - in
/logging/log4j/log4j2/trunk: RELEASE-NOTES.txt
src/changes/changes.xml /divdiv
/divAuthor: mattsicker
Date: Sun Aug
Original message
From: mattsic...@apache.org
Date:08/16/2014 23:25 (GMT-05:00)
To: comm...@logging.apache.org
Subject: svn commit: r1618449 - in /logging/log4j/log4j2/trunk:
RELEASE-NOTES.txt src/changes/changes.xml
Author: mattsicker
Date: Sun Aug 17 03:25:28 2014
...@logging.apache.org
Subject: svn commit: r1618449 - in /logging/log4j/log4j2/trunk:
RELEASE-NOTES.txt src/changes/changes.xml
Author: mattsicker
Date: Sun Aug 17 03:25:28 2014
New Revision: 1618449
URL: http://svn.apache.org/r1618449
Log:
Update release notes and changes
/trunk:
log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/util/PluginManager.java
src/changes/changes.xml /divdiv
/divAuthor: rpopma
Date: Sun Aug 10 07:09:36 2014
New Revision: 1617053
URL: http://svn.apache.org/r1617053
Log:
LOG4J2-769 Startup takes a long time if you have
.
Modified:
logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core/config/ConfigurationFactory.java
logging/log4j/log4j2/trunk/src/changes/changes.xml
Modified:
logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core/config
logging/log4j/log4j2/trunk/src/changes/changes.xml
Modified:
logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core/config/ConfigurationFactory.java
URL:
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core
.
Modified:
logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core/config/ConfigurationFactory.java
logging/log4j/log4j2/trunk/src/changes/changes.xml
Modified:
logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core/config
:
logging/log4j/log4j2/trunk/src/changes/changes.xml
Modified: logging/log4j/log4j2/trunk/src/changes/changes.xml
URL:
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/changes/changes.xml?rev=1612991r1=1612990r2=1612991view=diff
--
From: rpo...@apache.org
Date: 5 July 2014 20:58
Subject: svn commit: r1608149 - in /logging/log4j/log4j2/trunk:
log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerContextSelector.java
src/changes/changes.xml
To: comm...@logging.apache.org
Author: rpopma
Subject: svn commit: r1608149 - in /logging/log4j/log4j2/trunk:
log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerContextSelector.java
src/changes/changes.xml
To: comm...@logging.apache.org
Author: rpopma
Date: Sun Jul 6 01:58:13 2014
New Revision: 1608149
URL: http
src/changes/changes.xml
To: comm...@logging.apache.org
Author: rpopma
Date: Sun Jul 6 01:58:13 2014
New Revision: 1608149
URL: http://svn.apache.org/r1608149
Log:
LOG4J2-666: AsyncLoggerContextSelector should ensure that different
AsyncLoggerContext objects created by web application
...@apache.org
Date: 5 July 2014 20:58
Subject: svn commit: r1608149 - in /logging/log4j/log4j2/trunk:
log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerContextSelector.java
src/changes/changes.xml
To: comm...@logging.apache.org
Author: rpopma
Date: Sun Jul 6 01:58:13 2014
/changes/changes.xml
To: comm...@logging.apache.org
Author: rpopma
Date: Sun Jul 6 01:58:13 2014
New Revision: 1608149
URL: http://svn.apache.org/r1608149
Log:
LOG4J2-666: AsyncLoggerContextSelector should ensure that different
AsyncLoggerContext objects created by web application
--
From: rpo...@apache.org
Date: 5 July 2014 20:58
Subject: svn commit: r1608149 - in /logging/log4j/log4j2/trunk:
log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerContextSelector.java
src/changes/changes.xml
To: comm...@logging.apache.org
Author: rpopma
Date: Sun Jul 6
/apache/logging/log4j/core/async/AsyncLoggerContextSelector.java
src/changes/changes.xml
To: comm...@logging.apache.org
Author: rpopma
Date: Sun Jul 6 01:58:13 2014
New Revision: 1608149
URL: http://svn.apache.org/r1608149
Log:
LOG4J2-666: AsyncLoggerContextSelector should ensure
Author: tschoening
Date: Fri Mar 14 11:40:27 2014
New Revision: 1577488
URL: http://svn.apache.org/r1577488
Log:
LOGCXX-430: LogManager::getRootLogger is not thread-safe
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp/logmanager.cpp
Author: tschoening
Date: Mon Mar 10 07:15:07 2014
New Revision: 1575851
URL: http://svn.apache.org/r1575851
Log:
LOGCXX-411: Fixed this in LOGCXX-394.
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL:
http
Author: joseph
Date: Mon Mar 3 18:10:39 2014
New Revision: 1573645
URL: http://svn.apache.org/r1573645
Log:
LOGCXX-416
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL:
http://svn.apache.org/viewvc/incubator/log4cxx
Author: tschoening
Date: Mon Feb 10 13:33:17 2014
New Revision: 1566619
URL: http://svn.apache.org/r1566619
Log:
LOGCXX-319: Please make sure that the LOG4CXX_* macro's can be used as ordinary
statements.
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk
Author: tschoening
Date: Mon Feb 10 14:09:43 2014
New Revision: 1566628
URL: http://svn.apache.org/r1566628
Log:
LOGCXX-313: Build process fails in case of absence of iconv support in apr-util
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp
Author: tschoening
Date: Mon Feb 10 14:17:26 2014
New Revision: 1566630
URL: http://svn.apache.org/r1566630
Log:
LOGCXX-337: Suggested fix for socketappender not reconnecting multiple times
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp
Author: tschoening
Date: Mon Feb 10 14:32:56 2014
New Revision: 1566638
URL: http://svn.apache.org/r1566638
Log:
LOGCXX-368: method and class name functions not properly implemented
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp
Author: tschoening
Date: Mon Feb 10 15:19:34 2014
New Revision: 1566655
URL: http://svn.apache.org/r1566655
Log:
LOGCXX-394: Levels are not thread safe
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp/level.cpp
Modified: incubator/log4cxx
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/include/log4cxx/log4cxx.hw
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/changes/changes.xml?rev=1566676r1=1566675r2=1566676view
Author: tschoening
Date: Sun Feb 9 18:08:41 2014
New Revision: 1566338
URL: http://svn.apache.org/r1566338
Log:
LOGCXX-367: Build fails on Linux with g++ 4.4
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/examples/cpp/console.cpp
incubator
/changes.xml
Modified: incubator/log4cxx/trunk/liblog4cxx.pc.in
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/liblog4cxx.pc.in?rev=1566339r1=1566338r2=1566339view=diff
==
--- incubator/log4cxx/trunk/liblog4cxx.pc.in
Author: tschoening
Date: Sun Feb 9 18:13:41 2014
New Revision: 1566340
URL: http://svn.apache.org/r1566340
Log:
LOGCXX-382: Mingw build type conversion error
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/include/log4cxx/helpers/thread.h
Author: tschoening
Date: Sun Feb 9 19:50:54 2014
New Revision: 1566379
URL: http://svn.apache.org/r1566379
Log:
LOGCXX-358: SMTPAppender generating Emails with an empty body
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp/smtpappender.cpp
Author: tschoening
Date: Sun Feb 9 19:59:31 2014
New Revision: 1566384
URL: http://svn.apache.org/r1566384
Log:
LOGCXX-388: Hierarchy::updateParents loops forever on illegal logger-name like
'.logger1'
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk
Author: tschoening
Date: Mon Feb 10 06:02:52 2014
New Revision: 1566514
URL: http://svn.apache.org/r1566514
Log:
LOGCXX-353: When a client disconnects the SocketHubAppender crashes on the next
log message
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk
/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/examples/cpp/Makefile.am
incubator/log4cxx/trunk/src/main/cpp/Makefile.am
incubator/log4cxx/trunk/src/test/cpp/Makefile.am
Copied: incubator/log4cxx/trunk/configure.ac (from r1562805,
incubator/log4cxx/trunk/configure.in
:
incubator/log4cxx/trunk/liblog4cxx.pc.in
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/liblog4cxx.pc.in
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/liblog4cxx.pc.in?rev=1562823r1=1562822r2=1562823view=diff
Author: rhys
Date: Thu Jan 30 13:58:42 2014
New Revision: 1562827
URL: http://svn.apache.org/r1562827
Log:
Properly order change entries
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL:
http://svn.apache.org/viewvc
Author: tschoening
Date: Sun Jan 19 16:43:17 2014
New Revision: 1559520
URL: http://svn.apache.org/r1559520
Log:
Issues were sorted nummerical mainly, fixed the others.
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL
/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/changes/changes.xml?rev=1559523r1=1559522r2=1559523view=diff
Author: joseph
Date: Sat Jan 11 16:27:39 2014
New Revision: 1557417
URL: http://svn.apache.org/r1557417
Log:
added changes from prior commits
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL:
http://svn.apache.org
Author: tschoening
Date: Tue Jan 7 08:38:24 2014
New Revision: 1556144
URL: http://svn.apache.org/r1556144
Log:
Fixed indentation
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL:
http://svn.apache.org/viewvc/incubator
1 - 100 of 304 matches
Mail list logo
