[PATCH] doc: Fix typo (missing period)

DoneSubmitted by Pierre Neidhardt.
Details
2 participants
  • Pierre Neidhardt
  • Marius Bakke
Owner
unassigned
Severity
normal
P
P
Pierre Neidhardt wrote on 21 Jul 2018 22:34
(address . guix-patches@gnu.org)
20180721203417.512-1-ambrevar@gmail.com
* HACKING (Commit Access): Fix typo.--- HACKING | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Toggle diff (15 lines)diff --git a/HACKING b/HACKINGindex d1a26d2d6..f68753fee 100644--- a/HACKING+++ b/HACKING@@ -27,7 +27,7 @@ mailing list. When you get commit access, please make sure to follow the policy below (discussions of the policy can take place on guix-devel@gnu.org.) Non-trivial patches should always be posted to guix-patches@gnu.org (trivial-patches include fixing typos, etc.) This mailing list fills the+patches include fixing typos, etc.). This mailing list fills the patch-tracking database at [[https://bugs.gnu.org/guix-patches]]; see "Contributing" in the manual for details. -- 2.17.1
P
P
Pierre Neidhardt wrote on 21 Jul 2018 22:37
(address . 32244@debbugs.gnu.org)
87muukqq8p.fsf@gmail.com
I know it's the most trivial patch ever but since I just got commitaccess I don't want to slip on my first commit! :p
So... This is a typo, right? (Sorry for being so pedantic!)
-- Pierre Neidhardt
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAltTmaYACgkQm9z0l6S7zH9L/Af/QEM49Q5DaxMiaSJh6qWfLUjc9o4JZkVE4XaU7bOZ7I2k6qFVenqB+E+OGfvNf9Yq+dEiznrzg1cSFS3sbzy2M4ILDmk45z/j+KtLYJo4mc26SLwPVnq/Zit4JLLm0++Z0LVAc/w32iOm3XNjBDKRZ7bdT+7vAE7sYxxVSu2cpwRUGu78Ur+WuPeFANhG3cEzvuYbJbHx9XG5C7ZHL3NxLGJ+PO8BN/2wa4EqJZfHqI5kvKrKT+q2tgfTYc0ENHbSqc5pa8Bxm+9UZUySxZngBpJUonLmhbUj3ILAP61X8lgMo4Lr6PZcnc0Xin0pEjQdnq39n+rzd0VjRJ+TqW6/Pg===M5UR-----END PGP SIGNATURE-----
M
M
Marius Bakke wrote on 22 Jul 2018 16:25
Re: [bug#32244] [PATCH] doc: Fix typo (missing period)
87fu0b5ov0.fsf@fastmail.com
Hello Pierre,
Congratulations on commit access! Make sure to read HACKI...oh.
Pierre Neidhardt <ambrevar@gmail.com> writes:
Toggle quote (2 lines)> * HACKING (Commit Access): Fix typo.
LGTM!
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAltUk+MACgkQoqBt8qM6VPr9ZAf/YVSVKzo9XAQir+ckQ4YqJymAjcWlDPjufw1QpQ3ssxp8+Qvr5xallfFoqm2aPUMJZN2FYnYU2SdlwNLTJZ5seHP16pykHC4uBD+MjJ8wsZORmLQYvbSutFlGHI2wNmMoJdFWjJ1LfIIsQ2noZYLpSrgizufBe/ois6ksjF5xNWxDr4gUZL3if+W3pnQZ+ds8PC7aubZX02UjZXWujy+wu5mx82Lvbo1+X8AMJMkLCMpqPDAFXQhENRs+end63WqX4rQO5DFCeg6TbI0Ufji5GRK+dE1WuekEEw4+f9TaGZRK3BZ9USc3m/gwMDKklyt8oXfhApNPgG94R3iDfzP/ag===8rao-----END PGP SIGNATURE-----
P
P
Pierre Neidhardt wrote on 22 Jul 2018 17:12
(name . Marius Bakke)(address . mbakke@fastmail.com)(address . 32244@debbugs.gnu.org)
87pnzfpamd.fsf@gmail.com
Thanks!
(Magit made me too fast again and I pushed the wrong branch... I think I cleanedup the mess though.)
-- Pierre Neidhardt
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAltUnvoACgkQm9z0l6S7zH9oCwf+KMUU6M8WGPMdMgZBlzwUOasTI+DOsPmOyyBImx/zWFb0ujS39exXVP4V08GVVL1Qc5Aje0iZ3Sq5l0z0Rg6sC/SUdiTaqUxVAF0Ck1P1w6e2mkU0GwIOW9bRtIA9R63kInSV2kaGCDP8vmnUxvFgZMSetkq5Hke+z9Akk6dOl+fHJFdKfN8nkc1cZnPz3zkRY+4kcAMm9+7SrVg3XlZkXAGrcMapc3jVrqgvB1vyf6maCf77KS6UYJ1zDUMg2d6DowiKEXdcFZB7B3Jyf9yx12g1qgeygrOimZVSJaSfI9HFSch/2ydUUl/AiLHnItC9bwPity40ZzaKqqbD6b7y0g===b+5x-----END PGP SIGNATURE-----
P
P
Pierre Neidhardt wrote on 22 Jul 2018 17:20
control message for bug #32244
(address . control@debbugs.gnu.org)
87o9ezpa9m.fsf@gmail.com
tags 32244 fixedclose 32244
P
P
Pierre Neidhardt wrote on 22 Jul 2018 17:22
Re: [bug#32244] [PATCH] doc: Fix typo (missing period)
(name . Marius Bakke)(address . mbakke@fastmail.com)(address . 32244@debbugs.gnu.org)
87muujpa5z.fsf@gmail.com
Bit confused with debbugs: I've closed the issue with`debbugs-gnu-send-control-message', passing "done" to it and using a smtpserver.
Is it the correct way? Is "done" the right message (there are so many ofthem...). Does it matter which smtp server / e-mail I use?
-- Pierre Neidhardt
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAltUoUgACgkQm9z0l6S7zH94hQf/QjdiBZ3CFXmzy3yNmLhumB7Q79rZKrRTZapgIlkiI9f0O0xAxCHSsTED+rhVLCulPrmjsRfmMkwa4XEns9bcpsz/G4u/RFStM+C77XYvHaxyqcThujmdc4aoyeJqM3q6TL0cnexw88lR41TOR6rJXGx/bdz7Fub1V4/9nAWH+Fyz0EvTkbpl5BM2+PKsGdM3U04M2yDi28RkgKV6PRRKfIOTNguLhOnIcvECZ3wiu7rnTQrmKuVave22s1DwGndsjJZFgxUJ1Ked5E1xNB5ldlvTsHiqBUI+SIt6MtToiW9sjzwDKKUTCszgZRt3Lf7LO6HL2p1JCsSZSYkrfdqcFQ===Ib9S-----END PGP SIGNATURE-----
M
M
Marius Bakke wrote on 22 Jul 2018 17:35
(name . Pierre Neidhardt)(address . ambrevar@gmail.com)(address . 32244-done@debbugs.gnu.org)
87zhyj472e.fsf@fastmail.com
Pierre Neidhardt <ambrevar@gmail.com> writes:
Toggle quote (7 lines)> Bit confused with debbugs: I've closed the issue with> `debbugs-gnu-send-control-message', passing "done" to it and using a smtp> server.>> Is it the correct way? Is "done" the right message (there are so many of> them...). Does it matter which smtp server / e-mail I use?
Looks good to me: https://bugs.gnu.org/32244.
Note: you can also simply CC <bugid-done>@debbugs.gnu.org to close itwith an email message. I did it now for clarity.
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAltUpDkACgkQoqBt8qM6VPpFPggAm0a0ndBUaEocg4zFpuezshDGI4LFOkCQKs+KRVvX0Rmepu7PVy6j43yH6fPST5PNKVpPyRAXOCyrVg8aGd3GUwPoBRo6InSGMy3YmSJOH35zTOF1+Pao8mLJcbQ/0KvOxYNUXlGQK8UQH6Yf0Npe5vmvkXOtmW9rMZyb8w/4a4PdQEi8LZ4x5IagwwdhnEr1O8nrFROBz0OTKfYGdMUVBuJFQsWPzD2rtvgi58VkIeOlPha5dMyWn9StsuZvj+OtrnHC3Cb41HTVIpfv/hkV1iE7tpoqaqi5v+fFMLs12PDC7vThP9O6wLJzgbVIe5e0ujI/fjYrSwcNtE1vstAUXg===nuN6-----END PGP SIGNATURE-----
Closed
?
Your comment

This issue is archived.

To comment on this conversation send email to 32244@debbugs.gnu.org