All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Bence Ferdinandy <bence@ferdinandy.com>
Cc: git@vger.kernel.org, "Fővárosi Vízművek Zrt." <noreply@vizmuvek.hu>
Subject: Re: [PATCH v10 0/8] set-head/fetch remote/HEAD updates
Date: Tue, 22 Oct 2024 13:39:38 -0400	[thread overview]
Message-ID: <ZxfjWnZF4EbtVH12@nand.local> (raw)
In-Reply-To: <20241021134354.705636-1-bence@ferdinandy.com>

On Mon, Oct 21, 2024 at 03:36:57PM +0200, Bence Ferdinandy wrote:
> Bence Ferdinandy (8):
>   t/t5505-remote: set default branch to main
>   refs: atomically record overwritten ref in update_symref
>   remote set-head: refactor for readability
>   remote set-head: better output for --auto
>   refs: add TRANSACTION_CREATE_EXISTS error
>   refs: add create_only option to refs_update_symref_extended
>   fetch: set remote/HEAD if it does not exist
>   fetch set_head: handle mirrored bare repositories

After applying this topic to 'seen', I noticed some new CI breakage that
appears to be caused by this topic:

    https://github.com/git/git/actions/runs/11449483611/job/31855171514#step:4:2506

After dropping the topic locally and building with 'make SANITIZE=leak'
and then running t0410-partial-clone.sh, I was able to resolve the
failures.

Would you mind building with 'SANITIZE=leak' and running that script to
see if you can address the issue? Thanks.

Thanks,
Taylor

  parent reply	other threads:[~2024-10-22 17:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1088915169.629942.1729445083543@FVRT-HAMMYAS-P.vizmuvek.hu>
2024-10-21 13:36 ` [PATCH v10 0/8] set-head/fetch remote/HEAD updates Bence Ferdinandy
2024-10-21 13:36   ` [PATCH v10 1/8] t/t5505-remote: set default branch to main Bence Ferdinandy
2024-10-21 13:36   ` [PATCH v10 2/8] refs: atomically record overwritten ref in update_symref Bence Ferdinandy
2024-10-21 13:37   ` [PATCH v10 3/8] remote set-head: refactor for readability Bence Ferdinandy
2024-10-21 13:37   ` [PATCH v10 4/8] remote set-head: better output for --auto Bence Ferdinandy
2024-10-21 13:37   ` [PATCH v10 5/8] refs: add TRANSACTION_CREATE_EXISTS error Bence Ferdinandy
2024-10-21 13:37   ` [PATCH v10 6/8] refs: add create_only option to refs_update_symref_extended Bence Ferdinandy
2024-10-21 13:37   ` [PATCH v10 7/8] fetch: set remote/HEAD if it does not exist Bence Ferdinandy
2024-10-21 13:37   ` [PATCH v10 8/8] fetch set_head: handle mirrored bare repositories Bence Ferdinandy
2024-10-21 20:43   ` [PATCH v10 0/8] set-head/fetch remote/HEAD updates Taylor Blau
2024-10-21 21:06     ` Bence Ferdinandy
2024-10-22 17:39   ` Taylor Blau [this message]
2024-10-22 18:33     ` Bence Ferdinandy
2024-10-22 19:04       ` Taylor Blau
2024-10-22 19:09         ` Bence Ferdinandy

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=ZxfjWnZF4EbtVH12@nand.local \
    --to=me@ttaylorr.com \
    --cc=bence@ferdinandy.com \
    --cc=git@vger.kernel.org \
    --cc=noreply@vizmuvek.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.