[PR #660] [MERGED] Refixed s3fs_init message(ref #652) #1590

New issue

Closed

opened 2026-03-04 02:01:12 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 02:01:12 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/660
Author: @ggtakec
Created: 10/15/2017
Status: ✅ Merged
Merged: 10/15/2017
Merged by: @ggtakec

Base: master ← Head: patch

📝 Commits (1)

1eba27a Refixed s3fs_init message(ref #652)

📊 Changes

2 files changed (+9 additions, -1 deletions)

View changed files

📝 src/common.h (+8 -0)
📝 src/s3fs.cpp (+1 -1)

📄 Description

Relevant Issue (if applicable)

#652

Details

I noticed that there was a problem with fixing #652.
s3fs init message was always output when CRIT level.
However, if we changed to the INFO level for this message, it will not be output unless the s3fs log output level specification is less than INFO.
The init message level should be INFO, but it should be outputted independently of the log output level of s3fs.
I fixed this again.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/660 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 10/15/2017 **Status:** ✅ Merged **Merged:** 10/15/2017 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `patch` --- ### 📝 Commits (1) - [`1eba27a`](https://github.com/s3fs-fuse/s3fs-fuse/commit/1eba27a50a2539fcdb34074870690b57df543f85) Refixed s3fs_init message(ref #652) ### 📊 Changes **2 files changed** (+9 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/common.h` (+8 -0) 📝 `src/s3fs.cpp` (+1 -1) </details> ### 📄 Description #### Relevant Issue (if applicable) #652 #### Details I noticed that there was a problem with fixing #652. s3fs init message was always output when CRIT level. However, if we changed to the INFO level for this message, it will not be output unless the s3fs log output level specification is less than INFO. The init message level should be INFO, but it should be outputted independently of the log output level of s3fs. I fixed this again. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>