From: Vineet Gupta <vineetg@rivosinc.com>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Deletion of gcc branch devel/vineetg/optim-double-const-m0
Date: Thu, 24 Aug 2023 13:36:44 -0700 [thread overview]
Message-ID: <2f7805d1-3e1c-7d84-ead2-85c5934dd8c4@rivosinc.com> (raw)
Hi,
I have write access to gcc repo and ended up creating a personal dev
branch in improper namespace which I can no longer force push to (or
even delete).
Can you please nuke # devel/vineetg/optim-double-const-m0 @
git+ssh://gcc.gnu.org/git/gcc.git
Thx,
-Vineet
reply other threads:[~2023-08-24 20:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2f7805d1-3e1c-7d84-ead2-85c5934dd8c4@rivosinc.com \
--to=vineetg@rivosinc.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).