From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: Packaging Jami progress Date: Mon, 6 Jan 2020 23:40:08 +0100 Message-ID: References: <20191215211230.66fea79e@interia.pl> <875zihclep.fsf@elephly.net> <20191222002815.4db8e9ca@interia.pl> <87d0cgpzqo.fsf@elephly.net> <20191223204317.3069e8ba@kompiuter> <20191225023416.0b36b90c@kompiuter> <20191227195731.6b869970@interia.pl> <20191227224639.5b7d1e74@interia.pl> <8736d4kcue.fsf@ambrevar.xyz> <20200101162246.677552a6@kompiuter> <87tv5d2gn1.fsf@elephly.net> <20200104011328.5c5ab586@kompiuter> <87woa7xmem.fsf@ambrevar.xyz> <20200106192326.498f2afe@interia.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:59108) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iob2w-0003KX-TJ for guix-devel@gnu.org; Mon, 06 Jan 2020 17:40:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iob2v-0000XJ-GU for guix-devel@gnu.org; Mon, 06 Jan 2020 17:40:26 -0500 Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]:34626) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iob2r-0000Ri-B7 for guix-devel@gnu.org; Mon, 06 Jan 2020 17:40:21 -0500 Received: by mail-qt1-x835.google.com with SMTP id 5so43794073qtz.1 for ; Mon, 06 Jan 2020 14:40:21 -0800 (PST) In-Reply-To: <20200106192326.498f2afe@interia.pl> 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: Jan Cc: Guix Devel Hi Jan, Thank you for working on Jami. Cool! On Mon, 6 Jan 2020 at 20:09, Jan wrote: > > I just closed all 22 issues that I improperly started. How should I > send the patches to create just one issue? When git send-email asks me > if I want to send the patches, should I send only one and then wait? > How long? I tried sending the rest a few seconds later, but it didn't > work as indended. Or should I send one mail to guix-patches@gnu.org and > then send the rest to NNN@debbugs.gnu.org? I copy/paste what I wrote here [1], waiting to improve the manual or the cookbook. --8<---------------cut here---------------start------------->8--- The next step is to commit the changes. In this case, three commits (one per package) seem nice. Give a look to previous commits as example of commit message (ChangeLog format, etc.). Now, it is time to prepare the submission: git format-patch --cover-letter -o patches master this will create the 3 patches in the folder patches/ and one cover letter. Edit the cover letter to describe what the patches are about then submit it to the bug tracker: git send-email --to=guix-patches@gnu.org patches/0000-cover-letter.patch Wait the answer to the bug tracker. You should receive an email (if your .gitconfig is ok) with the bug number. Last submit the patches: git send-email --to=ABCDEF@debbugs.gnu.org patches/000{1,2,3}-* where ABCDEF is the bug number. --8<---------------cut here---------------stop------------->8--- You can also run: rm patches/0000-cover-letter.patch git send-email --to=ABCDEF@debbugs.gnu.org patches/00* to send all the patches to the bug number ABCDEF. Be careful to not send twice the same patch. :-) Then you can also send normal email to ABCDEF@debbugs.gnu.org to discuss the patch. And another version (say version 2) of the patch series is produced with the git option --reroll-count=2 (in short -v2): git rebase -i / git amend / do your change git format-patch -v2 git send-email --to=ABCDEF@debbugs.gnu.org patches/v2-000* Note that you need to "guix install git:send-email". Hope that helps. All the best, simon [1] https://lists.gnu.org/archive/html/guix-devel/2019-10/msg00093.html