From: Hariom verma <hariom18599@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2020, #07; Thu, 27)
Date: Sat, 29 Aug 2020 18:56:52 +0530 [thread overview]
Message-ID: <CA+CkUQ_kBo6YW0x3QWnF+w8N33howU1CEosCmdANBoytwN=5WQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqo8muo5nt.fsf@gitster.c.googlers.com>
Hi,
On Sat, Aug 29, 2020 at 2:21 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> Hariom verma <hariom18599@gmail.com> writes:
>
> >> * hv/ref-filter-misc (2020-08-17) 9 commits
> >> (merged to 'next' on 2020-08-27 at c015fa6b0f)
> >> + ref-filter: add `sanitize` option for 'subject' atom
> >> + format-support: move `format_sanitized_subject()` from pretty
> >> + pretty: refactor `format_sanitized_subject()`
> >> + ref-filter: add `short` modifier to 'parent' atom
> >> + ref-filter: add `short` modifier to 'tree' atom
> >> + ref-filter: rename `objectname` related functions and fields
> >> + ref-filter: modify error messages in `grab_objectname()`
> >> + ref-filter: refactor `grab_objectname()`
> >> + ref-filter: support different email formats
> >>
> >> The "--format=" option to the "for-each-ref" command and friends
> >> learned a few more tricks, e.g. the ":short" suffix that applies to
> >> "objectname" now also can be used for "parent", "tree", etc.
> >>
> >> Will merge to 'master'.
> >
> > I sent an updated version of the patch series addressing your comment
> > concerning new file format-support.{c,h}[1].
>
> But other stuff (like format-sanitized-subject having unnecessary
> allocation and unnecessary special casing of LF) are worth fixing in
> the version queued above.
Yeah, I fixed that too in the v4 of the patch series.
> Let's revert the above out of 'next' and start afresh using v4.
Just saw v4 in the `seen` ;)
Thanks,
Hariom
next prev parent reply other threads:[~2020-08-29 18:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 21:43 What's cooking in git.git (Aug 2020, #07; Thu, 27) Junio C Hamano
2020-08-27 23:34 ` Jeff King
2020-08-27 23:36 ` Junio C Hamano
2020-08-28 0:39 ` Taylor Blau
2020-08-28 6:26 ` Jeff King
2020-08-28 8:31 ` Jeff King
2020-08-28 18:09 ` Taylor Blau
2020-08-28 2:16 ` Elijah Newren
2020-08-29 4:28 ` Matheus Tavares Bernardino
2020-08-28 15:48 ` ds/maintenance-part-[1-2] (was: What's cooking in git.git (Aug 2020, #07; Thu, 27)) Derrick Stolee
2020-08-28 20:09 ` What's cooking in git.git (Aug 2020, #07; Thu, 27) Hariom verma
2020-08-28 20:51 ` Junio C Hamano
2020-08-29 13:26 ` Hariom verma [this message]
2020-08-29 10:13 ` Hariom verma
2020-08-29 18:28 ` Junio C Hamano
2020-08-29 13:20 ` Hariom verma
2020-08-29 18:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+CkUQ_kBo6YW0x3QWnF+w8N33howU1CEosCmdANBoytwN=5WQ@mail.gmail.com' \
--to=hariom18599@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.
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).