From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "René Scharfe" <l.s.r@web.de>,
"Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
"Phillip Wood" <phillip.wood@dunelm.org.uk>,
"Daniel Li" <dan@danielyli.com>,
git@vger.kernel.org
Subject: Re: the state of diff_free() and release_revisions()
Date: Fri, 20 May 2022 10:23:25 -0700 [thread overview]
Message-ID: <xmqqczg8jeya.fsf@gitster.g> (raw)
In-Reply-To: <220520.86pmk81a9z.gmgdl@evledraar.gmail.com> (=?utf-8?B?IsOG?= =?utf-8?B?dmFyIEFybmZqw7Zyw7A=?= Bjarmason"'s message of "Fri, 20 May 2022 17:23:01 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> AFAICT the current status in this area is that with 2cc712324d5 (Merge
> branch 'rs/fast-export-pathspec-fix', 2022-05-04) and 5048b20d1c2 (Merge
> branch 'rs/format-patch-pathspec-fix', 2022-05-04) merged the known bugs
> related to this have been fixed, along with 3da993f2e63 (Merge branch
> 'jc/diff-tree-stdin-fix', 2022-04-28).
There is another possible known breakage around "diff -I --cc"
reported, no?
https://lore.kernel.org/git/a6a14213-bc82-d6fb-43dd-5a423c40a4f8@web.de/
> Not coincidentally around the same time my ab/plug-leak-in-revisions got
> un-marked for "next" from [1] to [2], and I'm looking for a path forward
> for this whole thing...
I think this was not because it had known bugs but only because we
wanted to avoid distractions and too much churns in the tree.
I think it is a good time to reactivate it; Phillip Wood took a
serious look at the latest round, if I am reading [*] correctly.
* https://lore.kernel.org/git/2cc2d026-1496-1ed9-838b-6fdf8cfba285@gmail.com/
Thanks.
next prev parent reply other threads:[~2022-05-20 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 2:22 Bug: `git show` honors path filters only for the first commit Daniel Li
2022-04-30 4:59 ` Junio C Hamano
2022-04-30 5:29 ` [PATCH] 2.36 show regression fix Junio C Hamano
2022-04-30 10:32 ` [PATCH] 2.36 format-patch " René Scharfe
2022-04-30 16:32 ` Carlo Marcelo Arenas Belón
2022-05-01 9:35 ` René Scharfe
2022-05-20 15:23 ` the state of diff_free() and release_revisions() (was: [PATCH] 2.36 format-patch regression fix) Ævar Arnfjörð Bjarmason
2022-05-20 17:23 ` Junio C Hamano [this message]
2022-04-30 14:31 ` [PATCH] 2.36 fast-export regression fix René Scharfe
2022-04-30 20:50 ` 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=xmqqczg8jeya.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=carenas@gmail.com \
--cc=dan@danielyli.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=phillip.wood@dunelm.org.uk \
/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).