From: Karthik Nayak <karthik.188@gmail.com>
To: Ivan Chernyavsky <camposer@yandex.ru>
Cc: Junio C Hamano <gitster@pobox.com>,
Duy Nguyen <pclouds@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Which branch(es) contain certain commits? (was Re: (unknown))
Date: Sat, 22 Aug 2015 16:29:55 +0530 [thread overview]
Message-ID: <CAOLa=ZRdYKqSjT90VRW0qOeQ9YG6xN0QojrhUwrar2V1DyHe5w@mail.gmail.com> (raw)
In-Reply-To: <2689531440235153@web22m.yandex.ru>
On Sat, Aug 22, 2015 at 2:49 PM, Ivan Chernyavsky <camposer@yandex.ru> wrote
>
>> Note that "branch --list", "tag --list" and "for-each-ref" are being
>> revamped to share more internal code. If you want to pursue this,
>> you probably would want to build on top of that effort once it is
>> done. That way, you may get "tag --grep=FIX123" for free.
>>
>
> This is interesting. So can I have a look on some repo/branch or just wait until it'll be merged?
>
This should be what you're looking for:
http://thread.gmane.org/gmane.comp.version-control.git/276363
http://thread.gmane.org/gmane.comp.version-control.git/276377
This is the current progress, the rest is in git/next.
There is still a series of porting the printing part of branch.c to be done.
--
Regards,
Karthik Nayak
prev parent reply other threads:[~2015-08-22 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 12:47 (unknown) Ivan Chernyavsky
2015-08-05 17:03 ` Which branch(es) contain certain commits? (was Re: (unknown)) Junio C Hamano
2015-08-05 17:05 ` Junio C Hamano
2015-08-05 19:48 ` Ivan Chernyavsky
2015-08-15 9:19 ` Duy Nguyen
2015-08-17 6:45 ` Which branch(es) contain certain commits? (was Re: (unknown)) Ivan Chernyavsky
2015-08-17 17:49 ` Junio C Hamano
2015-08-21 21:29 ` Which branch(es) contain certain commits? (was Re: (unknown)) Ivan Chernyavsky
2015-08-21 22:39 ` Junio C Hamano
2015-08-22 9:19 ` Ivan Chernyavsky
2015-08-22 10:32 ` Ivan Chernyavsky
2015-08-22 10:59 ` Karthik Nayak [this message]
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='CAOLa=ZRdYKqSjT90VRW0qOeQ9YG6xN0QojrhUwrar2V1DyHe5w@mail.gmail.com' \
--to=karthik.188@gmail.com \
--cc=camposer@yandex.ru \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).