From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:43228) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iyCEW-0001qS-BA for guix-patches@gnu.org; Sun, 02 Feb 2020 05:12:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iyCEU-0006Z6-AW for guix-patches@gnu.org; Sun, 02 Feb 2020 05:12:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:33576) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iyCEU-0006Z0-64 for guix-patches@gnu.org; Sun, 02 Feb 2020 05:12:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iyCEU-0002GZ-17 for guix-patches@gnu.org; Sun, 02 Feb 2020 05:12:02 -0500 Subject: [bug#39292] [PATCH 10/10] gnu: Add rapid-photo-downloader Resent-Message-ID: References: <680004635.33218.1580636177883@office.mailbox.org> From: Christopher Baines In-reply-to: <680004635.33218.1580636177883@office.mailbox.org> Date: Sun, 02 Feb 2020 11:11:16 +0100 Message-ID: <87tv49guyj.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Sebastian Schott Cc: "39292@debbugs.gnu.org" <39292@debbugs.gnu.org> --=-=-= Content-Type: text/plain Sebastian Schott writes: > Hi Chris, > > thank you very much for your suggestions and explanations (somehow > your messages did not reach my mail inbox). Now I got some work to do, > but I am not quite sure on how to proceed. Should I step back in my > local git history, apply the corrections and resend the patches or can > I just go on and patch my patches? I guess everything should go to the > initial bug tracking number? Hi Sebastian, Sorry for the email issues, I had an issue with my mailserver, but it should be fixed now. The way you've split your changes across commits is good, so ideally just tweak the commits. If you're familiar with interactive rebasing in Git, you can use that to make the changes. Don't worry too much about it though, it's the end result that's the most important. Once you've had a go at iterating the patches, just send them again to the bug email address. Just let me know if you have any questions :) Thanks, Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl42oERfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XeNiw/+O5UROrr0LXyqvHmHzas8knb5TYXC6Zy5dPr+iaPmgtgjJhEOajIjtZ6Y nNTxWLiH/QsLjo6yhNVFVE/hmYgWZDIzmSgfQtPMUaDakAfbTw1q5v1HZWDLuqAm zFE0ExmMA8vief0LW0yotiWlhd5q4CBoNa6gQLIPvY8OMhED23boPh/LTsYckH2X j0hwMVgBY62n77Y5BMG99dpBlCER4eWu4vr/p1TylghQmXpcJ3BjSDfkM/NyLs8V CbEbo2nKFGj+HBixNeU8AyS9ocQ9uumce1bBJmput7m7x2b8jU3gvLk7RksE3/Q+ RzfTCXHrABqv07AYf78OhDLO0vsLGv1BnRiuHgdMVFC2lB4AyKK6HEPosNkMegTm pH8jxbHIix/7uMV+b7C40RrsXKStPl93j58a21CK4xxJfZWsLvVTf9W7LWO3wZ/c vbNe1jUm9YqhS5NneRMdTgBzd6c8Vy7upyKUqxb9smG2dyRa459Wh2M3aOtc6noV JiLOfBkKmQgHJHBiD3/PT6n57r9lf+mFsdnRexvbngWCYfyx58bL8jZ/zVrMLCMS vuQYt6eiWIjXug2Uz/ISkmm1+RVfmhng/QIsuKZWt0Bhh2TEps6BnsVuNlPWUjt2 xtpkUixHjPN7yawlykil/GlVdbPOnmJgkQX7zQcuZLJNwfpNd8o= =T1/M -----END PGP SIGNATURE----- --=-=-=--