From: "Eric Sun (ericsun2)" <ericsun2@cisco.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: bridge-utils: request to fix git tags
Date: Fri, 12 Dec 2025 02:26:02 +0000 [thread overview]
Message-ID: <161B0C34-1F18-4010-B89B-738DA12F77DC@cisco.com> (raw)
Hello,
The bridge-utils git repo [1] has several tags that cause recent-ish git fsck
to fail with the missingSpaceBeforeDate error [2]. This is frustrating when
working with github, where such cosmetic errors are not ignored by default as
they are by other platforms (e.g. gitlab).
Though bridge-utils is deprecated, I was hoping somebody with access might be
willing to fix up the tags?
I've verified that something like [3, see: "How to work around that issue..."]
address it correctly.
Thanks in advance!
[1] https://git.kernel.org/pub/scm/network/bridge/bridge-utils.git
[2] https://git-scm.com/docs/git-fsck#Documentation/git-fsck.txt-missingSpaceBeforeDate
[3] https://sunweavers.net/blog/node/36
Cisco Confidential
next reply other threads:[~2025-12-12 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 2:26 Eric Sun (ericsun2) [this message]
2025-12-12 4:00 ` bridge-utils: request to fix git tags Stephen Hemminger
2025-12-12 6:14 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161B0C34-1F18-4010-B89B-738DA12F77DC@cisco.com \
--to=ericsun2@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox