From: Daniel Campbell <zlg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] repo/gentoo.git, or how committing is challenging
Date: Sun, 13 Dec 2015 22:23:20 -0800 [thread overview]
Message-ID: <566E6058.5020802@gentoo.org> (raw)
In-Reply-To: <20151213190045.1e186781.dolsen@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 12/13/2015 07:00 PM, Brian Dolbec wrote:
> [snip]
>
>
I just wanted to say that I didn't have (too) much trouble setting up
my key when I was getting started back in May. I couldn't have done it
without your assistance; I believe one other person helped me out,
too. I went to #gentoo-keys and you guys went over it step by step.
It looks like my key is still good, too.
If you need any help with the project, Brian, I wouldn't mind
contributing. Specifically the documentation. I'd just need an idea of
where to start.
- --
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWbmBTAAoJEAEkDpRQOeFwYNEQAId2kLObVWr8RmK/jhD8iD5a
nmTdGi54SeDBYLVufYAq6u6O6xE9RJT0bb8uI2/Yy2ux+ZFGyALNIf736AjS9j15
vCmcnC0QrGXIMCfRMGtbRLdacqFGU0Ov59MyF3mzuFVElqW2YafFDGE0s6uZjt8m
ElC9Q/tewBHAFYbALUxQcYsY6V5xdVkxRBsBRKfE2HaOEnYma6oRcdefYuVHfhEm
Jtn9X+E+pAT8fSoskyQhTMmu4NUBonHcqeZBaWrZmIzKs8w8fdK8Z2Jw4QqzT+Fc
6QclX/BBmrEM8V9649ywaINYXWlOGKVe9PKUlMyr29qJ54azmGFW6LuakTaIpmtc
W2q7JpdL3bX7IREEsLl2+DHAcGIf4GRihbNvEgT5JTGcRH2kf/NtDjHUP+pKdye6
NVlNmIQU8ZwB57n7fWniQFTzEZ5xoD0GGIPHCPAtku4+mnGhRinvJt4zrViPi+Mw
IwKnknKt72fs9kvmPO5o0zna9NdydkxWySU6Cq5jt6gMHcBwacztj+YXazcxL14y
Sb8ozV5mG2IlKL3ghJJhWuEbpMnWuW4XAu4EES5ZB2keXxFxVbpSNL6IDf2hyxxY
AUYHLyTD+aaab0dPsGrddg8iQt+pbH+WxKduhqtGFg8QdYT9AaE5iAZxGMehg+kA
Vpo7Lk1Glb9qYRVCJ+Lg
=EdQ8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-12-14 6:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 17:36 [gentoo-dev] repo/gentoo.git, or how committing is challenging Patrick Lauer
2015-12-13 17:38 ` Patrick Lauer
2015-12-13 18:50 ` Andrew Savchenko
2015-12-13 19:05 ` Patrick Lauer
2015-12-13 19:20 ` Andrew Savchenko
2015-12-13 21:30 ` Mike Gilbert
2015-12-13 21:53 ` Andrew Savchenko
2015-12-14 3:00 ` Brian Dolbec
2015-12-14 6:23 ` Daniel Campbell [this message]
2015-12-14 11:12 ` Patrick Lauer
2015-12-14 17:52 ` Mike Gilbert
2015-12-15 0:31 ` Peter Stuge
2015-12-21 3:21 ` [gentoo-dev] " Ryan Hill
2015-12-21 18:59 ` Peter Stuge
2015-12-22 0:45 ` Rich Freeman
2015-12-22 9:41 ` Patrick Lauer
2015-12-22 12:08 ` Rich Freeman
2015-12-22 12:53 ` Patrick Lauer
2015-12-22 13:14 ` Rich Freeman
2015-12-22 13:31 ` Patrick Lauer
2015-12-22 14:04 ` Rich Freeman
2015-12-22 18:21 ` Patrick Lauer
2015-12-22 23:55 ` Peter Stuge
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=566E6058.5020802@gentoo.org \
--to=zlg@gentoo.org \
--cc=gentoo-dev@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