From: Jeff King <peff@peff.net>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Nov 2015, #03; Fri, 20)
Date: Mon, 23 Nov 2015 13:58:12 -0500 [thread overview]
Message-ID: <20151123185812.GC2597@sigill.intra.peff.net> (raw)
In-Reply-To: <CAOLa=ZRpvd-Nd9HiZMt6aZF9bi5i1MHNDZUSdUsGC9C-t+2bSg@mail.gmail.com>
On Mon, Nov 23, 2015 at 12:02:35AM +0530, Karthik Nayak wrote:
> > * kn/for-each-branch-remainder (2015-10-02) 9 commits
> > - branch: implement '--format' option
> > - branch: use ref-filter printing APIs
> > - ref-filter: make %(upstream:track) prints "[gone]" for invalid upstreams
> > - ref-filter: introduce format_ref_array_item()
> > - ref-filter: adopt get_head_description() from branch.c
> > - ref-filter: modify "%(objectname:short)" to take length
> > - ref-filter: add support for %(path) atom
> > - ref-filter: implement %(if:equals=<string>) and %(if:notequals=<string>)
> > - ref-filter: implement %(if), %(then), and %(else) atoms
> >
> > More unification among "branch -l", "tag -l" and "for-each-ref --format".
> >
> > Expecting a reroll.
> > ($gmane/278926)
> >
>
> This series is supposed to follow this:
> http://thread.gmane.org/gmane.comp.version-control.git/281180 which I
> recently sent.
> So replace "for-each-branch-remainder" with this in "Whats cooking"?
Thanks, it was on my "leftover topics to pick up" list. I'll make sure
it gets updated in the next cycle.
-Peff
next prev parent reply other threads:[~2015-11-23 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 14:09 What's cooking in git.git (Nov 2015, #03; Fri, 20) Jeff King
2015-11-22 18:32 ` Karthik Nayak
2015-11-23 18:58 ` Jeff King [this message]
2015-11-23 9:06 ` Luke Diamand
2015-11-23 18:58 ` Jeff King
2015-11-23 13:09 ` Johannes Schindelin
2015-11-23 18:57 ` Jeff King
2015-11-23 14:00 ` Victor Leschuk
2015-11-24 9:53 ` Michael J Gruber
2015-11-24 20:43 ` Jeff King
2015-11-24 22:04 ` Max Kirillov
2015-11-24 22:06 ` Jeff King
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=20151123185812.GC2597@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.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.
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 NNTP newsgroup(s).