From: Lorenzo Pegorari <lorenzo.pegorari2002@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
Patrick Steinhardt <ps@pks.im>,
Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>
Subject: Re: [GSoC PATCH v2 2/4] pack-write: add helper to fill promisor file after repack
Date: Thu, 26 Mar 2026 17:15:02 +0100 [thread overview]
Message-ID: <acVbhqGEc2826Cii@lorenzo-VM> (raw)
In-Reply-To: <CAPig+cR7-3rdkHvGbzk8O7P=83pxBTvqXTUgMxYpf+OK9jNCgg@mail.gmail.com>
On Mon, Mar 23, 2026 at 04:27:44PM -0400, Eric Sunshine wrote:
> On Sun, Mar 22, 2026 at 3:18 PM LorenzoPegorari
> <lorenzo.pegorari2002@gmail.com> wrote:
> > Create a `copy_all_promisor_files()` helper function used to copy the
> > contents of all ".promisor" files in a `repository` inside another
> > ".promisor" file.
> >
> > This function can be used to preserve the contents of all ".promisor"
> > files inside a new ".promisor" file, for example when a repack happens.
> >
> > This function is written in such a way so that it will read all the
> > ".promisor" files inside the given `repository` line by line, and copy
> > only the lines that are not already present in the destination file. This
> > is done to avoid copying the same lines multiple times that may come from
> > multiple (redundant) packfiles. There might be another better/cleaner way
> > to achieve this.
> >
> > Signed-off-by: LorenzoPegorari <lorenzo.pegorari2002@gmail.com>
> > ---
>
> Thanks, I think this version addresses all my review comments[*] and
> looks much better overall. Use of `strset` makes a big difference over
> the previous attempt. A couple minor comments below...
>
> [*]: https://lore.kernel.org/git/CAPig+cQSsMfvHJnwuXGQ1Je8ekz=Rqbaibn-3shbya5y-5xTKg@mail.gmail.com/
>
> > diff --git a/pack-write.c b/pack-write.c
> > @@ -621,3 +622,63 @@ void write_promisor_file(const char *promisor_name, struct ref **sought, int nr_
> > +void copy_all_promisor_files(struct repository *repo, const char *promisor_name)
> > +{
> > + struct strset dest_content = STRSET_INIT;
> > + struct strbuf read_line = STRBUF_INIT;
> > + struct strbuf promisor_source_name = STRBUF_INIT;
> > + struct strbuf write_dest = STRBUF_INIT;
> > + FILE *dest, *source;
> > + struct packed_git *p;
> > + int err;
>
> Nit: I probably would have declared `FILE *dest` within the scope of
> the repo_for_each_pack() loop as suggested in the review, but it's not
> worth a reroll.
Ack. I will fix it. Thanks!
> > + dest = xfopen(promisor_name, "r+");
> > + while (strbuf_getline(&read_line, dest) != EOF)
> > + strset_add(&dest_content, read_line.buf);
> > +
> > + repo_for_each_pack(repo, p) {
> > + if (!p->pack_promisor)
> > + continue;
> > +
> > + strbuf_reset(&promisor_source_name);
> > + strbuf_addstr(&promisor_source_name, p->pack_name);
> > + strbuf_strip_suffix(&promisor_source_name, ".pack");
> > + strbuf_addstr(&promisor_source_name, ".promisor");
> > + source = xfopen(promisor_source_name.buf, "r");
> > +
> > + /*
> > + * For each line of the promisor source file, check if it already
> > + * is in the promisor dest file. If not, add it to write_dest, so
> > + * that it will be written in the dest file.
> > + */
> > + while (strbuf_getline(&read_line, source) != EOF) {
> > + if (strset_add(&dest_content, read_line.buf)) {
> > + strbuf_addbuf(&write_dest, &read_line);
> > + strbuf_addstr(&write_dest, "\n");
>
> Not worth a reroll, but this could also be:
>
> strbuf_addch(&write_dest, '\n');
Ack.
> > + }
> > + }
> > +
> > + err = ferror(source);
> > + err |= fclose(source);
> > + if (err)
> > + die(_("could not read '%s' promisor file"), promisor_source_name.buf);
> > + }
> > +
> > + if (write_dest.len) {
> > + strbuf_strip_suffix(&write_dest, "\n");
> > + if (fseek(dest, 0L, SEEK_END))
> > + die_errno(_("fseek failed"));
> > + fprintf(dest, "%s\n", write_dest.buf);
> > + }
>
> Can you explain why you strip "\n" and then re-add it via fprintf()?
> The reason is not immediately obvious.
Stripping it and then adding it again is actually not necessary. I think
it was necessary in a previous iteration. Thanks for noticing, will fix!
> > + err = ferror(dest);
> > + err |= fclose(dest);
> > + if (err)
> > + die(_("could not write '%s' promisor file"), promisor_name);
> > +
> > + strbuf_release(&read_line);
> > + strbuf_release(&promisor_source_name);
> > + strbuf_release(&write_dest);
> > + strset_clear(&dest_content);
> > +}
>
> Everything appears to be released. Good.
Thank you so much for your help Eric,
Lorenzo
next prev parent reply other threads:[~2026-03-26 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 21:28 [GSoC PATCH 0/3] preserve promisor files content after repack LorenzoPegorari
2026-03-21 21:28 ` [GSoC PATCH 1/3] pack-write: add explanation to promisor file content LorenzoPegorari
2026-03-21 21:28 ` [GSoC PATCH 2/3] pack-write: add helper to fill promisor file after repack LorenzoPegorari
2026-03-22 2:04 ` Eric Sunshine
2026-03-22 18:50 ` Lorenzo Pegorari
2026-03-21 21:29 ` [GSoC PATCH 3/3] repack-promisor: preserve content of promisor files " LorenzoPegorari
2026-03-22 19:16 ` [GSoC PATCH v2 0/4] preserve promisor files content " LorenzoPegorari
2026-03-22 19:16 ` [GSoC PATCH v2 1/4] pack-write: add explanation to promisor file content LorenzoPegorari
2026-03-23 21:07 ` Junio C Hamano
2026-03-25 21:33 ` Lorenzo Pegorari
2026-03-22 19:18 ` [GSoC PATCH v2 2/4] pack-write: add helper to fill promisor file after repack LorenzoPegorari
2026-03-23 20:27 ` Eric Sunshine
2026-03-26 16:15 ` Lorenzo Pegorari [this message]
2026-03-23 21:30 ` Junio C Hamano
2026-03-26 2:01 ` Lorenzo Pegorari
2026-03-22 19:18 ` [GSoC PATCH v2 3/4] repack-promisor: preserve content of promisor files " LorenzoPegorari
2026-03-23 21:48 ` Junio C Hamano
2026-03-26 2:12 ` Lorenzo Pegorari
2026-03-22 19:18 ` [GSoC PATCH v2 4/4] t7700: test for promisor file content " LorenzoPegorari
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=acVbhqGEc2826Cii@lorenzo-VM \
--to=lorenzo.pegorari2002@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=newren@gmail.com \
--cc=ps@pks.im \
--cc=sunshine@sunshineco.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