home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Area 51 - Testing Area
switch to a new logging framework (Log4Net)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="elliottmc" data-source="post: 975170" data-attributes="member: 14268"><p>In the original branch</p><p> </p><p><a href="https://github.com/MediaPortal/MediaPortal-1/commits/FEAT-3273-Switch_to_log4net" target="_blank">https://github.com/MediaPortal/MediaPortal-1/commits/FEAT-3273-Switch_to_log4net</a></p><p> </p><p>we only have four commits changing a total of 18 files. The new branch changes 4940 files. I think it is fair to say something is definitely wrong.</p><p> </p><p>Is it possible to see how the four specific commits in the previous branch apply to master?</p></blockquote><p></p>
[QUOTE="elliottmc, post: 975170, member: 14268"] In the original branch [url]https://github.com/MediaPortal/MediaPortal-1/commits/FEAT-3273-Switch_to_log4net[/url] we only have four commits changing a total of 18 files. The new branch changes 4940 files. I think it is fair to say something is definitely wrong. Is it possible to see how the four specific commits in the previous branch apply to master? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
switch to a new logging framework (Log4Net)
Contact us
RSS
Top
Bottom