wxiaoguang 65d3e1161b Fix sub-command log level (#25537) ... More fix for #24981 * #24981 Close #22361 * #22361 There were many patches for Gitea's sub-commands to satisfy the facts: * Some sub-commands shouldn't output any log, otherwise the git protocol would be broken * Sometimes the users want to see "verbose" or "quiet" outputs That's a longstanding problem, and very fragile. This PR is only a quick patch for the problem. In the future, the sub-command system should be refactored to a clear solution. ---- Other changes: * Use `ReplaceAllWriters` to replace `RemoveAllWriters().AddWriters(writer)`, then it's an atomic operation. * Remove unnecessary `syncLevelInternal` calls, because `AddWriters/addWritersInternal` already calls it. Co-authored-by: Giteabot <teabot@gitea.io>		2023-06-28 08:02:06 +02:00
..
color_console_other.go
color_console_windows.go
color_console.go
color_router.go
color.go
event_format_test.go
event_format.go
event_writer_base.go
event_writer_conn_test.go
event_writer_conn.go
event_writer_console.go
event_writer_file.go
event_writer.go
flags_test.go
flags.go
groutinelabel_test.go
groutinelabel.go
init.go
level_test.go
level.go
logger_global.go	Fix sub-command log level (#25537)	2023-06-28 08:02:06 +02:00
logger_impl.go	Fix sub-command log level (#25537)	2023-06-28 08:02:06 +02:00
logger_test.go
logger.go
manager_test.go	Fix sub-command log level (#25537)	2023-06-28 08:02:06 +02:00
manager.go
misc.go
stack.go