From: Andreas Heiduk <asheiduk@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: RFC: How should we handle un-deleted remote branches?
Date: Sun, 22 Apr 2018 09:41:42 +0200 [thread overview]
Message-ID: <3fcd1b50-2aeb-0ea4-fea7-b5705e76c027@gmail.com> (raw)
In-Reply-To: <87in8mdqhr.fsf@evledraar.gmail.com>
Am 20.04.2018 um 14:14 schrieb Ævar Arnfjörð Bjarmason:
> But this is a possible work-around:
>
> git init /tmp/empty.git
> git remote add avar file:///tmp/empty.git
> git remote prune avar
> git remote remove avar
This won't do it also?
git remote prune origin
> I started to patch this, but I'm not sure what to do here. we could do
> some combination of:
>
> 0. Just document the current behavior and leave it.
>
> 1. Dig further down to see what other remotes reference these refs, and
> just ignore any refspecs that don't explicitly reference
> refs/remotes/<our_deleted_remote>/*.
>
> I.e. isn't the intention here to preserve a case where you have two
> URLs for the same effective remote, not whene you have something
> like a --mirror refspec? Unfortunately I can't ask the original
> author :(
>
> 2. Warn about each ref we didn't delete, or at least warn saying
> there's undeleted refs under refs/remotes/<name>/*.
>
> 3. Make 'git remote remove --force-deletion <name>' (or whatever the
> flag is called) be a thing. But unless we do the next item this
> won't be useful.
>
> 4. Make 'git remote prune <name>' work in cases where we don't have a
> remote called <name> anymore, just falling back to deleting
> refs/remotes/<name>. In this case 'git remote remove
> --force-deletion <name>' would also do the same thing.
Possible 5):
Don't fix "git remote remove" but "git remote add" to complain that its
ref-namespace is already occupied by some other remote. Add "--force"
for the experts.
next prev parent reply other threads:[~2018-04-22 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 12:14 RFC: How should we handle un-deleted remote branches? Ævar Arnfjörð Bjarmason
2018-04-22 7:41 ` Andreas Heiduk [this message]
2018-04-22 11:17 ` Ævar Arnfjörð Bjarmason
2018-04-22 14:30 ` Andreas Heiduk
2018-04-22 18:37 ` Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fcd1b50-2aeb-0ea4-fea7-b5705e76c027@gmail.com \
--to=asheiduk@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).