From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Karthik Nayak <Karthik.188@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)
Date: Tue, 7 Feb 2017 01:24:09 +0100 [thread overview]
Message-ID: <CAM0VKjmhO9NQLz9TDv5M3OhxSBt-JdjaouVT0pTA-a6mGaF4_A@mail.gmail.com> (raw)
In-Reply-To: <xmqqzihzymn3.fsf@gitster.mtv.corp.google.com>
> * sg/completion-refs-speedup (2017-02-06) 13 commits
> - squash! completion: fill COMPREPLY directly when completing refs
> - completion: fill COMPREPLY directly when completing refs
> - completion: list only matching symbolic and pseudorefs when completing refs
> - completion: let 'for-each-ref' sort remote branches for 'checkout' DWIMery
> - completion: let 'for-each-ref' filter remote branches for 'checkout' DWIMery
> - completion: let 'for-each-ref' strip the remote name from remote branches
> - completion: let 'for-each-ref' and 'ls-remote' filter matching refs
> - completion: don't disambiguate short refs
> - completion: don't disambiguate tags and branches
> - completion: support excluding full refs
> - completion: support completing full refs after '--option=refs/<TAB>'
> - completion: wrap __git_refs() for better option parsing
> - completion: remove redundant __gitcomp_nl() options from _git_commit()
> (this branch uses sg/completion.)
>
> Will hold.
> This seems to break 9902 when merged to 'pu'.
All failing tests fail with the same error:
fatal: unrecognized %(refname:strip=2) argument: strip=2
That's because of this topic:
> * kn/ref-filter-branch-list (2017-01-31) 20 commits
> (merged to 'next' on 2017-01-31 at e7592a5461)
> + branch: implement '--format' option
> + branch: use ref-filter printing APIs
> + branch, tag: use porcelain output
> + ref-filter: allow porcelain to translate messages in the output
> + ref-filter: add an 'rstrip=<N>' option to atoms which deal with refnames
> + ref-filter: modify the 'lstrip=<N>' option to work with negative '<N>'
> + ref-filter: Do not abruptly die when using the 'lstrip=<N>' option
> + ref-filter: rename the 'strip' option to 'lstrip'
And in particular this commit, which, well, does what it's subject
says it's doing, thus breaking backwards compatibility.
> + ref-filter: make remote_ref_atom_parser() use refname_atom_parser_internal()
> + ref-filter: introduce refname_atom_parser()
> + ref-filter: introduce refname_atom_parser_internal()
> + ref-filter: make "%(symref)" atom work with the ':short' modifier
> + ref-filter: add support for %(upstream:track,nobracket)
> + ref-filter: make %(upstream:track) prints "[gone]" for invalid upstreams
> + ref-filter: introduce format_ref_array_item()
> + ref-filter: move get_head_description() from branch.c
> + ref-filter: modify "%(objectname:short)" to take length
> + ref-filter: implement %(if:equals=<string>) and %(if:notequals=<string>)
> + ref-filter: include reference to 'used_atom' within 'atom_value'
> + ref-filter: implement %(if), %(then), and %(else) atoms
>
> The code to list branches in "git branch" has been consolidated
> with the more generic ref-filter API.
>
> Will cook in 'next'.
next prev parent reply other threads:[~2017-02-07 0:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 22:34 What's cooking in git.git (Feb 2017, #02; Mon, 6) Junio C Hamano
2017-02-07 0:24 ` SZEDER Gábor [this message]
2017-02-07 1:17 ` Jacob Keller
2017-02-07 20:01 ` Junio C Hamano
2017-02-09 0:25 ` Stefan Beller
2017-02-09 1:01 ` Junio C Hamano
2017-02-09 3:46 ` Jeff King
2017-02-09 5:09 ` Junio C Hamano
2017-02-10 21:17 ` Junio C Hamano
2017-02-09 12:29 ` Johannes Schindelin
2017-02-09 17:20 ` Junio C Hamano
2017-02-09 20:37 ` Johannes Schindelin
2017-02-09 22:02 ` Junio C Hamano
2017-02-09 22:32 ` Johannes Schindelin
2017-02-09 16:08 ` Michael Haggerty
2017-02-09 19:18 ` Junio C Hamano
2017-02-09 19:24 ` Junio C Hamano
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=CAM0VKjmhO9NQLz9TDv5M3OhxSBt-JdjaouVT0pTA-a6mGaF4_A@mail.gmail.com \
--to=szeder.dev@gmail.com \
--cc=Karthik.188@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).