Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: b4 shazam not stripping ---
Date: Thu, 9 May 2024 14:43:48 +0100	[thread overview]
Message-ID: <65ab295c-e613-4367-a4a1-2cd04581fd29@citrix.com> (raw)
In-Reply-To: <20240509-victorious-lean-mamba-4e77b7@lemur>

On 09/05/2024 2:40 pm, Konstantin Ryabitsev wrote:
> On Thu, May 09, 2024 at 01:05:40AM GMT, Andrew Cooper wrote:
>> Hello,
>>
>> b4 shazam 33b93fdf-bf16-49b8-aec2-0b2c19f5c471@suse.com
>>
>> is leaving the notes under --- in the commit message of the finalised patch.
> We aren't doing anything beyond passing everything to "git am", so if 
> this is happening, it's not really something b4 is not doing correctly.
>
> I can't test your example above, unfortunately, because I don't know 
> against which tree this patch is (I've tried xen tip, but that's not 
> it).
>
> Can you let me know what repo I need to fetch to be able to apply that 
> patch?

It is xen tip, as long as you've pulled up master within the past 2
weeks.  I happened to be testing on top of a2330b51df2.

But if its git-am going wrong, then probably the only option is to keep
vigilance for it happening.

~Andrew

  reply	other threads:[~2024-05-09 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09  0:05 b4 shazam not stripping --- Andrew Cooper
2024-05-09 13:40 ` Konstantin Ryabitsev
2024-05-09 13:43   ` Andrew Cooper [this message]
2024-05-09 13:47     ` Konstantin Ryabitsev
2024-05-09 13:48 ` Konstantin Ryabitsev
2024-05-09 13:50 ` Kernel.org Bugbot
2024-05-09 14:50 ` Kernel.org Bugbot
2024-05-09 15:05 ` Konstantin Ryabitsev
2024-05-09 15:09   ` Andrew Cooper

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=65ab295c-e613-4367-a4a1-2cd04581fd29@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@kernel.org \
    /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