From mboxrd@z Thu Jan  1 00:00:00 1970
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=manjaro.org header.i=@manjaro.org header.b="mnxxlBUl"
Received: from mail.manjaro.org (mail.manjaro.org [116.203.91.91])
	by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C327FBF
	for <git@vger.kernel.org>; Sat, 25 Nov 2023 04:28:16 -0800 (PST)
Precedence: bulk
X-Mailing-List: git@vger.kernel.org
List-Id: <git.vger.kernel.org>
List-Subscribe: <mailto:git+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:git+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=manjaro.org; s=2021;
	t=1700915294;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=p0GB9F9A0pXEHyEfYZ4FJR8skBtZVumLQId82PGgqQQ=;
	b=mnxxlBUl2IylTOsD/zmsbtLZWYB3gS8eO/Y5v2SKaHC7TURTloHn1lh7Onv8/2HsTi9mDp
	w2IpB7/0vAp6kHuBMGazuHA+JBV2PedzIecZW/6EaoIXeft+2TgLiAbK+5hJBxMxH/Xm5f
	YITgmZMUEN+3oenjquUdIoXyWv2tUmdcloROg0OKB8XWd86/U6/C2RVkS1KwtUX6jrgbH2
	EQLybM1bjc9Yh5L1fohEuyu8Re5XWzEvicjhO1SBpmxV2v8QbhPUmd57vs7HfWhGysHKXH
	oDM9cvQ5upRC8s4FBMhv0oBMSzi4LrBSmhEPnydEKwWlR7Q0rEi1UFm4fzJceA==
Date: Sat, 25 Nov 2023 13:28:13 +0100
From: Dragan Simic <dsimic@manjaro.org>
To: "H.Merijn Brand" <linux@tux.freedom.nl>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Git Mailing List
 <git@vger.kernel.org>
Subject: Re: Fix git-send-email.perl w.r.t. recent Getopt::Long update
In-Reply-To: <20231125104211.5b7fe0be@pc09>
References: <20231124103932.31ca7688@pc09> <ZWFaZcgzwEP13geI@archie.me>
 <20231125104211.5b7fe0be@pc09>
Message-ID: <449722c7e6ab8bddae44133f2a97491d@manjaro.org>
X-Sender: dsimic@manjaro.org
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Authentication-Results: ORIGINATING;
	auth=pass smtp.auth=dsimic@manjaro.org smtp.mailfrom=dsimic@manjaro.org

On 2023-11-25 10:45, H.Merijn Brand wrote:
> As I am used to PR's by now on all OSS projects I am involved in, or
> use git commits or merges directly on the repo, I *never* use
> format-patch and/or send-email.

Actually, using email to send patches is quite neat, IMHO, once you get 
hold of it.

> These docs - yes I read them - do not offer a concise cut-n-paste
> example for people like me. In order to have my relative simple patch
> submitted (I already had the PR ready, but that came with a huge
> warning that PR's are not accepted) I did it the way I did it. Now I
> need to read and learn two new commands> I don't think that is very
> user-friendly, but that might be just me.
> 
> Ironically, this patch is about the mail part of git.
> 
> I suggest adding a small example like
> 
>  # Create the patch basics
>  $ git format-patch --cover-letter -M origin/master -o outgoing
>  # Fix the subject
>  $ $VISUAL outgoing/0000-cover-letter.patch
>  # Send the mail
>  $ git send-email --to=git@vger.kernel.org outgoing/*

Please note that a cover letter isn't needed unless you're sending a 
patch series, i.e. unless you're generating and sending more than a 
single patch at once.  Also, fixing the subject line inside the patch 
files generated by git-format-patch shouldn't be needed in most cases, 
and commit summaries should be adjusted/rebased instead, if needed.