From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Binutils <binutils@sourceware.org>, GDB <gdb@sourceware.org>
Subject: Re: How can I remove a personal tag?
Date: Tue, 01 Mar 2016 01:05:00 -0000 [thread overview]
Message-ID: <CAMe9rOrX4q7hJ3CDJ+03aLMbhri2T4SpPDYm1KNuHD5-JW9zKw@mail.gmail.com> (raw)
In-Reply-To: <20160229235006.GB1710@adacore.com>
On Mon, Feb 29, 2016 at 3:50 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> I want to update users/hjl/linux/release/2.26.51.0.1 tag by
>> removing it fist. I got
>>
>> # git push origin :users/hjl/linux/release/2.26.51.0.1
>> remote: *** Deleting a tag is not allowed in this repository
>> remote: error: hook declined to update
>> refs/tags/users/hjl/linux/release/2.26.51.0.1
>> Auto packing the repository for optimum performance.
>> warning: There are too many unreachable loose objects; run 'git prune'
>> to remove them.
>> To ssh://hjl@sourceware.org/git/binutils-gdb.git
>> ! [remote rejected] users/hjl/linux/release/2.26.51.0.1 (hook declined)
>> error: failed to push some refs to
>> 'ssh://hjl@sourceware.org/git/binutils-gdb.git'
>
> Changing the target of a tag is considered to be a really bad idea.
> I have to run, but you can look it up on the web as to why.
>
> I can delete the tag for you, but regardless, I recommend you use
Can you delete it for me? Thanks.
BTW, can you also prune the git repo? It has too many unreachable
objects.
> another one. This happened to me too when I was creating an earlier
> GDB release, so it's really important to be careful when creating
> them...
>
> --
> Joel
--
H.J.
next prev parent reply other threads:[~2016-03-01 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 22:56 H.J. Lu
2016-02-29 23:50 ` Joel Brobecker
2016-03-01 1:05 ` H.J. Lu [this message]
2016-03-01 16:47 ` Joel Brobecker
2016-03-01 17:07 ` H.J. Lu
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=CAMe9rOrX4q7hJ3CDJ+03aLMbhri2T4SpPDYm1KNuHD5-JW9zKw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb@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