public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Shreyansh Paliwal <shreyanshpaliwalcmsmn@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git am: apply patches directly via message id
Date: Thu, 19 Mar 2026 08:35:29 -0700	[thread overview]
Message-ID: <xmqqjyv7n872.fsf@gitster.g> (raw)
In-Reply-To: <20260319152313.1324081-1-shreyanshpaliwalcmsmn@gmail.com> (Shreyansh Paliwal's message of "Thu, 19 Mar 2026 20:51:11 +0530")

Shreyansh Paliwal <shreyanshpaliwalcmsmn@gmail.com> writes:

>> Sounds a lot like "b4 am -o-" piped to "git am" to me.
>
> I see. Though I think b4 is an external library, and I am reckoning that
> this functionality is used commonly so would it make sense to add this
> natively in git am ? or it is fine using b4 for this.

But lore (and the way it takes the message-ID and returns not just a
single message but a mbox with all patches in a complete series) is
very specific external dependency.  It does not belong to "git am",
whose only purpose is to accept a mailbox with bunch of patches (and
we do not care how you downloaded the mailbox) and create commits
out of them.  Interacting with lore and downloading patches from it
is what "b4" does and it does it well.

So, no, it is not _fine_ using b4 for this.  It is crazy not to use
it for this.

  reply	other threads:[~2026-03-19 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19  9:23 [RFC] git am: apply patches directly via message id Shreyansh Paliwal
2026-03-19 13:43 ` Junio C Hamano
2026-03-19 15:21   ` Shreyansh Paliwal
2026-03-19 15:35     ` Junio C Hamano [this message]
2026-03-19 15:45       ` Shreyansh Paliwal

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=xmqqjyv7n872.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=shreyanshpaliwalcmsmn@gmail.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