From: Joel Brobecker <brobecker@adacore.com>
To: overseers@sourceware.org
Subject: non-fatal error pushing to gdb's htdocs Git repository
Date: Sun, 3 Mar 2024 10:38:04 +0400 [thread overview]
Message-ID: <ZeQazJQXjt1eWI6+@adacore.com> (raw)
Hello,
I pushed some commits to the htdocs repository
(ssh://sourceware.org/git/gdb-htdocs.git), and during the push I got
the following (non-fatal) error:
| $ git push origin main
| Enumerating objects: 21, done.
| Counting objects: 100% (21/21), done.
| Delta compression using up to 8 threads
| Compressing objects: 100% (11/11), done.
| Writing objects: 100% (12/12), 2.15 KiB | 2.15 MiB/s, done.
| Total 12 (delta 7), reused 0 (delta 0), pack-reused 0
| remote: error: unable to unlink old 'code-of-conduct/Code-Of-Conduct.html': Permission denied
| remote: error: unable to unlink old 'code-of-conduct/Committee.html': Permission denied
| remote: error: unable to unlink old 'code-of-conduct/Reporting-Guide.html': Permission denied
| To ssh://sourceware.org/git/gdb-htdocs.git
| cf657d6..0c59517 main -> main
Maybe something that happened during one of the hooks that update
the various websites?
Thank you,
--
Joel
next reply other threads:[~2024-03-03 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 6:38 Joel Brobecker [this message]
2024-03-03 13:09 ` Frank Ch. Eigler
2024-03-04 3:03 ` Joel Brobecker
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=ZeQazJQXjt1eWI6+@adacore.com \
--to=brobecker@adacore.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).