On 08/13/2011 06:30 AM, Stefan Bodewig wrote:
We do have a read-only git version at git://git.apache.org/log4net.git
http://git.apache.org/log4net.git/ mirrored at github as well
https://github.com/apache/log4net
Didn't know that. :-) Since that repository is read-only, it is not
exactly a
Can we start a discussion on the existing patches? Primary targets of
discussion are the ones I applied here:
https://bitbucket.org/NachbarsLumpi/log4net-patches/
This includes the unresolved issues containing a patch file:
* LOG4NET-190
* LOG4NET-108
* LOG4NET-270
--
Dominik Psenner
## OpenPGP
[
https://issues.apache.org/jira/browse/LOG4NET-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084561#comment-13084561
]
Dominik Psenner commented on LOG4NET-108:
-
Applied the existing patch here:
[
https://issues.apache.org/jira/browse/LOG4NET-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084565#comment-13084565
]
Dominik Psenner commented on LOG4NET-190:
-
Applied the existing patch here:
[
https://issues.apache.org/jira/browse/LOG4NET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084567#comment-13084567
]
Dominik Psenner commented on LOG4NET-271:
-
Applied the existing patch here:
[
https://issues.apache.org/jira/browse/LOG4NET-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084598#comment-13084598
]
Dominik Psenner commented on LOG4NET-235:
-
Applied the existing patch here:
I Agree.
Enviado desde BB
-Original Message-
From: Dominik Psenner (JIRA) j...@apache.org
Date: Sat, 13 Aug 2011 11:04:27
To: log4net-dev@logging.apache.org
Reply-To: Log4NET Dev log4net-dev@logging.apache.org
Subject: [jira] [Commented] (LOG4NET-221) Store log in database using
Who are those people? Maybe they should comment on this?
I am one of those people. At this point I have minimal (if any)
understanding of the actual patch insertion process, but given I don't
have write privileges that is okay. I also have minimal/no
understanding of how to apply patches that
On 2011-08-13, Dominik Psenner wrote:
There are 9 open issues targeted for 1.2.10. They should probably be
rescheduled to be included in 1.2.11?
I'm not even sure whether some of them still are relevant. They
certainly need to be rescheduled.
My preference would be to have some release like
On 2011-08-13, Dominik Psenner wrote:
On 08/13/2011 06:34 AM, Stefan Bodewig wrote:
For each of them we have to:
* see if the patches are not fixed already
* see if they fit into the current latest tip (trunk)
* revise if they include sane changes
* determine if they should be included
On 2011-08-13, Dominik Psenner wrote:
Can we start a discussion on the existing patches?
Absolutely. I'm running out of time right now, but will focus on the
three issues you've mentioned soon.
Stefan
On 2011-08-13, Roy Chastain wrote:
Who are those people? Maybe they should comment on this?
I am one of those people. At this point I have minimal (if any)
understanding of the actual patch insertion process, but given I don't
have write privileges that is okay. I also have minimal/no
On 2011-08-13, Stefan Bodewig wrote:
svn is pretty similar to TFS
The version control part of TFS that is.
There are differences but both have similar (limited) support for merge
tracking, perform branching in the file-system space (i.e. copy a trunk
dir to a branches/X_Y_Z dir) and both are
Thanks Stefan.
My immediate takeaway is that by using a distributed VCS we have the
capabilities that I am more used to in that we are working connected
instead of disconnected with the connection blocker being someone who
can commit in SVN on ASF.
Once we agree we have something that fits
On 2011-08-13, Roy Chastain wrote:
My immediate takeaway is that by using a distributed VCS we have the
capabilities that I am more used to in that we are working connected
instead of disconnected with the connection blocker being someone who
can commit in SVN on ASF.
Yes, BUT.
But once the
15 matches
Mail list logo