From: "Michał Górny" <mgorny@gentoo.org>
To: "haelwenn (lanodan) Monnier" <contact@hacktivis.me>,
gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] [PATCH] app-misc/pass-otp Version Bump
Date: Fri, 29 Jun 2018 11:37:23 +0200 [thread overview]
Message-ID: <1530265043.737.26.camel@gentoo.org> (raw)
In-Reply-To: <20180629025152.GA2924@NightmareMoon>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
W dniu pią, 29.06.2018 o godzinie 04∶51 +0200, użytkownik haelwenn
(lanodan) Monnier napisał:
> Hello,
> This is my first real-life try of sending patches via email, and by looking at the wiki[1], maybe the first on this list too.
>
> I’m using the mailing list because:
> - I’m not really confortable with having Github as a third-party, and it would be neat to not have only bugzilla as a tested alternative.
> - it’s documented in the wiki[1] as a possible way/alternative.
> - The github group have apparently been hacked ( CAAr7Pr9ijQMFE5U28p4M0H6Y+LKN5WRpzM_LAGq90juwuNsArw@mail.gmail.com )
>
> I’m also not sending a e-mail for each patch to avoid pollution on this mailing-list. Patches are linked as attachements so it’s easy to pick them up but feel free to inline them on your reviews.
>
Please pollute the mailing list using git format patches because:
a. replying to multiple attachments is just horrible,
b. archives.g.o doesn't allow fetching attachments.
Also, please wrap your mails.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
prev parent reply other threads:[~2018-06-29 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 2:51 [gentoo-proxy-maint] [PATCH] app-misc/pass-otp Version Bump haelwenn (lanodan) Monnier
2018-06-29 9:37 ` Michał Górny [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1530265043.737.26.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=contact@hacktivis.me \
--cc=gentoo-proxy-maint@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox