From: "Øystein Walle" <oystwa@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] for-each-ref: add %(upstream:gone) to mark missing refs
Date: Wed, 24 Aug 2016 20:26:26 +0200 [thread overview]
Message-ID: <CAFaJEqvm9Xj34t+F=KMtwRDEYhwHZ7=MRwsZ22-Gt_UPd4r72A@mail.gmail.com> (raw)
In-Reply-To: <20160824180730.mqlvhkthg4imd2vy@sigill.intra.peff.net>
Hi, Peff
On 24 August 2016 at 20:07, Jeff King <peff@peff.net> wrote
>
> Whoops, your v2 spurred me to review, but I accidentally read and
> responded to v1.
>
Thanks for the review! I was worried this patch had been buried :-)
In the mean time, however, I have discovered that this conflicts with
kn/ref-filter-branch-list in pu. In that topic this specific feature is
implemented as well. They incorporate it into %(upstream:track) instead
of having a separate "sub-atom" (what's the correct nomenclature, by the
way?) more in line with with branch -vv and your idea.
I recall seeing discussions about this work earlier, but I based my
patch on master and forgot to check pu. (It was a spur-of-the-moment
thing fueled by a question in #git about how to parse branch -vv to
delete all local branch who had their remote counter-parts removed after
a fetch --prune.)
Unless that topic gets rejected, or is known to not be merged for a
_long_ while, my patch doesn't add much value.
Regards,
Øsse
next prev parent reply other threads:[~2016-08-24 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 17:35 [PATCH v2] for-each-ref: add %(upstream:gone) to mark missing refs Øystein Walle
2016-08-24 18:07 ` Jeff King
2016-08-24 18:26 ` Øystein Walle [this message]
2016-08-24 18:33 ` Jeff King
2016-08-25 5:56 ` Karthik Nayak
2016-08-25 8:45 ` Øystein Walle
2016-08-26 6:31 ` Karthik Nayak
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='CAFaJEqvm9Xj34t+F=KMtwRDEYhwHZ7=MRwsZ22-Gt_UPd4r72A@mail.gmail.com' \
--to=oystwa@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).