Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Nextcloud
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TeDomum
Nextcloud
Commits
244c53de
Unverified
Commit
244c53de
authored
4 years ago
by
Christoph Wurst
Browse files
Options
Downloads
Patches
Plain Diff
Replace abandoned log normalizer with our fork
Signed-off-by:
Christoph Wurst
<
christoph@winzerhof-wurst.at
>
parent
4d64ec99
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
3rdparty
+1
-1
1 addition, 1 deletion
3rdparty
lib/private/Log.php
+1
-2
1 addition, 2 deletions
lib/private/Log.php
with
2 additions
and
3 deletions
3rdparty
@
e287243b
Compare
8f03ccac
...
e287243b
Subproject commit
8f03ccac97331ff781340d76a3f4a49a017d6ae1
Subproject commit
e287243b8eeaf72443b841ace3b1788e85a5aacd
This diff is collapsed.
Click to expand it.
lib/private/Log.php
+
1
−
2
View file @
244c53de
...
@@ -36,10 +36,9 @@ declare(strict_types=1);
...
@@ -36,10 +36,9 @@ declare(strict_types=1);
namespace
OC
;
namespace
OC
;
use
Nextcloud\LogNormalizer\Normalizer
;
use
OCP\Log\IDataLogger
;
use
OCP\Log\IDataLogger
;
use
function
array_merge
;
use
function
array_merge
;
use
InterfaSys\LogNormalizer\Normalizer
;
use
OC\Log\ExceptionSerializer
;
use
OC\Log\ExceptionSerializer
;
use
OCP\ILogger
;
use
OCP\ILogger
;
use
OCP\Log\IFileBased
;
use
OCP\Log\IFileBased
;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment