From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 8KLjGoiN/GCOZgEAgWs5BA (envelope-from ) for ; Sun, 25 Jul 2021 00:00:40 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id YKKCFoiN/GB9eQAA1q6Kng (envelope-from ) for ; Sat, 24 Jul 2021 22:00:40 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 4456225913 for ; Sun, 25 Jul 2021 00:00:40 +0200 (CEST) Received: from localhost ([::1]:55238 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7PhH-0001gP-Bj for larch@yhetil.org; Sat, 24 Jul 2021 18:00:39 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:35936) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7Pgr-0001g1-Rq for guix-devel@gnu.org; Sat, 24 Jul 2021 18:00:13 -0400 Received: from out2.migadu.com ([2001:41d0:2:aacc::]:27484) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7Pgo-0003pR-Qg for guix-devel@gnu.org; Sat, 24 Jul 2021 18:00:13 -0400 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1627164006; 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: in-reply-to:in-reply-to:references:references; bh=Fs6mvBG3EHD6MfBPQj8yJLArrJxK7glgbqQHUEZ+Muw=; b=GRkXl1urUKWgUdOXaFUT+zyTGQ6I9w+wgYIvQ17LxIekjuTREhDLSRJMAMJ2TuDgzCOTyr eyIJT+zfDNAlfrAs2fLToVZGQaYvehnJacqyQTXT7u05kqdCGxmRodHIrpLw9kY0xJtee3 yHY4Yu9SylWgw5HCqH2iqqGS+IUiKw9HKY90OgGSzPi3TWYs8/pay/D5F1u5Tls9D2GMNQ N4A8c1uJBRr+GPBPz6kBgYntvfWPTrF1dhXF+OKG17FOuQxzDLsLM9Q3qqecamuOy6oC81 A64wMPtJj5c3XMI5rvSbAMAtzqXHnpc5waBKYiKufPRx83O5EGExnM8ACxQj8w== From: Kyle Meyer To: Sarah Morgensen Subject: Re: Mailman From header rewrite In-Reply-To: <86h7gstbuw.fsf@mgsn.dev> References: <86h7gstbuw.fsf@mgsn.dev> Date: Sat, 24 Jul 2021 18:00:04 -0400 Message-ID: <875ywzpe3f.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Auth-User: kyle@kyleam.com Received-SPF: pass client-ip=2001:41d0:2:aacc::; envelope-from=kyle@kyleam.com; helo=out2.migadu.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -4.00 Authentication-Results: aspmx1.migadu.com; none X-Migadu-Queue-Id: 4456225913 X-Spam-Score: -4.00 X-Migadu-Scanner: scn0.migadu.com X-TUID: 8pkwaFnb2cqR Sarah Morgensen writes: > On Tuesday, January 5th, 2021 at 5:01 AM, Kyle Meyer wrote: > >> add the appropriate "From:" header to the body of each patch. `git am` >> will take the in-body header over the actual header. > > I wonder if there is a way to automate the duplication of the "From" > header into the body of the patch? I'm not aware of an existing way at the git level. Here's the only discussion I found about it on the git list: https://lore.kernel.org/git/305577c2-709a-b632-4056-6582771176ac@redhat.com/T/#u As a hacky/ugly way, for those that are okay tweaking the way their names ends up on the mailing list, they can adjust `send-email --from=` (or sendemail.from) slightly so that it doesn't match user.name/user.email, and then send-email should take care of adding an in-body header for user.name/user.email. Another option is of course to feed the patches to a custom post-processing script that adds the in-body "From:", where the details would depend a bit on the person's patch workflow. Or, moving that work a bit upstream, I think it'd be fairly straightforward to wire up a prepare-commit-msg hook that would insert an in-body "From:" (after checking some things, like whether the commit is being amended). I guess the main disadvantage of handling it at this spot is the risk of commits with in-body "From:" headers unintentionally being merged/pushed directly to the main line (given the person has commit access).