From: Jayati Shrivastava <gaurijove@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
Hariom verma <hariom18599@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: Having grep support the -o option
Date: Wed, 23 Mar 2022 23:15:56 +0530 [thread overview]
Message-ID: <CANsrJQc0c5w5iA99L_L8QpZTh_vSkDwXoq7zm2mKkZQtxzUH3Q@mail.gmail.com> (raw)
In-Reply-To: <220322.86a6dintod.gmgdl@evledraar.gmail.com>
On Tue, Mar 22, 2022 at 4:24 PM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
>
>
> On Tue, Mar 22 2022, Christian Couder wrote:
>
> > On Sun, Mar 20, 2022 at 8:14 PM Jayati Shrivastava <gaurijove@gmail.com> wrote:
> >>
> >> On Sat, Mar 19, 2022 at 9:49 PM Ævar Arnfjörð Bjarmason
> >> <avarab@gmail.com> wrote:
> >> >
> >> >
> >> > One thing I'd *really* like to see is the bits of %(if) %(then)
> >> > etc. extracted from ref-filter.c into some general API other commands
> >> > could use with strbuf_expand() and friends.
> >> >
> >> > I.e. if you could in addition to the strbuf_expand() callback define
> >> > what verbs you support for "if" and the like, or have callbacks for
> >> > their comparison functions.
> >> >
> >> > Then have that machinery drive the whole format expansion, which
> >> > eventually would expand your %(some-custom-thing) via a callback.
> >> >
> >> > I.e. the whole "valid_atom" state machine in ref-filter.c.
> >>
> >> So, the end goal is to design a formatting API that can be used by any
> >> command that takes --format option?
> >
> > It might be nice if we get closer to this after your GSoC project, but
> > I don't think it should become the main goal of the GSoC.
>
> Agreed. FWIW this is off-list discussion between Jayati and myself which
> started with her asking (and this was omitted in the context that made
> it on list:
>
> [...] Infact, I'll be excited to work on anything you suggest even
> if its not related to the project, as it will help me get familiar
> with the codebase and the contribution process at Git.
>
> So that suggestion of mine of generalizing ref-filter.c wasn't meant to
> distract from the GSoC project, I understood her to be looking for
> suggestions for things to work on that were *not* part of the GSoC
> project.
>
> So I suggested that ref-filter.c task, which is orthagonal, but relates
> to some of the same code.
I understand this might be out of scope for the gsoc project but I’ll
try to work in the
general direction of it.
I have been going through Hariom’s work from last year. He has
mentioned some failing
log tests for the new pretty library he implemented. I am currently
attempting to understand
these failures.
prev parent reply other threads:[~2022-03-23 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 21:20 [GSoC] Some #leftoverbits for anyone looking for little projects Ævar Arnfjörð Bjarmason
2019-05-20 18:23 ` Matheus Tavares
2019-05-20 23:49 ` Ævar Arnfjörð Bjarmason
2019-05-21 4:38 ` Matheus Tavares Bernardino
2019-05-28 10:37 ` Johannes Schindelin
2019-05-28 17:37 ` Matheus Tavares Bernardino
2019-05-28 18:16 ` Johannes Schindelin
2019-05-29 9:38 ` Johannes Schindelin
2019-05-29 9:40 ` Johannes Schindelin
[not found] ` <20220318220623.50528-1-gaurijove@gmail.com>
[not found] ` <CANsrJQdNKiX93GnVXztmvYQQBxr6-HsYNx5UvYXSFg32Op3ZPQ@mail.gmail.com>
[not found] ` <CANsrJQe1YuggxdBHdSdukXRj3myVCTNwLiiWNLrAzPpzA4FOOA@mail.gmail.com>
[not found] ` <220319.86ee2yds2f.gmgdl@evledraar.gmail.com>
[not found] ` <CANsrJQdJ1wBThUyJ=QSt6NwU8HzQY2VaWc11UfZQ+ktRQs_YTQ@mail.gmail.com>
[not found] ` <220319.86a6dlewyj.gmgdl@evledraar.gmail.com>
2022-03-20 19:14 ` Having grep support the -o option Jayati Shrivastava
2022-03-22 6:08 ` Christian Couder
2022-03-22 10:50 ` Ævar Arnfjörð Bjarmason
2022-03-23 17:45 ` Jayati Shrivastava [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
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=CANsrJQc0c5w5iA99L_L8QpZTh_vSkDwXoq7zm2mKkZQtxzUH3Q@mail.gmail.com \
--to=gaurijove@gmail.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@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.
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).