From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tobias Geerinckx-Rice Subject: Re: Please merge guix-patches bug: 36789-36800 Date: Wed, 24 Jul 2019 21:55:59 +0200 Message-ID: <87h87bi4vk.fsf@nckx> References: <87k1c7i81y.fsf@nckx> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39107) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hqNMs-0003Kj-AZ for guix-devel@gnu.org; Wed, 24 Jul 2019 15:56:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hqNMr-00019Q-4E for guix-devel@gnu.org; Wed, 24 Jul 2019 15:56:06 -0400 Received: from tobias.gr ([2001:470:7405::1]:49534) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hqNMq-00015D-EG for guix-devel@gnu.org; Wed, 24 Jul 2019 15:56:05 -0400 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: zimoun Cc: Guix Devel --=-=-= Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Zimoun, zimoun =E5=86=99=E9=81=93=EF=BC=9A > Hi Tobias, > > Thank you for your quick answer. You're very welcome. > On Wed, 24 Jul 2019 at 20:47, Tobias Geerinckx-Rice=20 > wrote: >> You can perform actions like this yourself by sending mail to >> control@debbugs.gnu.org. Here's some documentation[0] and a >> caveat[1]. > > I did not know. I thought that only person with super power=20 > could do that. Your implication that this is a huge potential security hole is=20 correct. And yet, strangely, it works in practice. > So I will do. > > However, I am not sure to understand how the merge needs to be=20 > ordered. > I have tried with 36789 and 36790. Your attempt looks successful to me[0]: =E2=80=9DMerged [snipped]. Request was from zimoun <=E2=80=A6> to control= @=E2=80=A6. (Wed, 24 Jul 2019 19:18:02 GMT)=E2=80=9D You should have got a confirmation e-mail as well. However=E2=80=A6 Note[0] that you were attempting to merge two=20 already-merged bugs. Merged bugs act as one flesh, so you got a=20 confusing response with all previous 11 numbers and the net effect=20 of your command was zero. >> What I do is to just manually write a cover letter in my MUA,=20 >> send >> it to guix-patches@, and wait for the response with the bug >> number. I have to keep an eye on my inbox anyway, so I don't=20 >> see >> the point of doing that on the command line. > > If I understand well, the basic workflow is: > > git format-patch -N --cover-letter -o patches Oh, I really meant =E2=80=98manually=E2=80=99 as in I fire up my MUA (emacs= in=20 this case), write a =E2=80=98sup geeks here's a patch series that frobs=20 foo=E2=80=99, add =E2=80=98[PATCH 0/n]=E2=80=99 to the subject by hand like= an animal,=20 and send it to guix-patches@. Does your command above generate a pretty diffstat or something?=20 It probably does. > edit patches/0000-cover-letter.patch > # send as you want patches/0000-cover-letter.patch to=20 > guix-patches@ > rm patches/0000-cover-letter.patch If you do want to send a *file* like this then yes, it is indeed=20 easier to use sendmail or a similar command-line tool. I don't=20 know the syntax for it by heart, though. > # wait the bug number > git send-email --to=3Dnnnnn@debbugs.gnu.org patches/*.patch Since I don't need to edit anything I don't write my patches to=20 the file system first. I use =E2=80=98git send-email =E2=80=A6 -7=E2=80=99= and away=20 they go. But this is getting into personal preference territory=20 :-) Kind regards, T G-R [0]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D36789#30 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQT12iAyS4c9C3o4dnINsP+IT1VteQUCXTi3zwAKCRANsP+IT1Vt eY17AQCY93s04a+d8evytfCKRdqKrXBpQye/1TyPmpWrBqNNLQD7BLzfCByoSi3g yyMoYgp4b1xmWuNz+BCiJhLhP+kI7AA= =HgM6 -----END PGP SIGNATURE----- --=-=-=--