From: Robert Cochran <robert-emacs@cochranmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 24362@debbugs.gnu.org
Subject: bug#24362: 25.1.50; Inconsistent docstring between pcase-let and pcase-let*
Date: Mon, 26 Sep 2016 16:39:09 -0700 [thread overview]
Message-ID: <87h992p6xu.fsf@cochranmail.com> (raw)
In-Reply-To: <87bmzcgics.fsf@web.de> (Michael Heerdegen's message of "Sun, 25 Sep 2016 16:32:51 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Don't you want to get commit access?
Sure I would, but I figure that I don't have the required amount of
'known-ness' to bother requesting this access right now. I'd have
imagined I'd need to have a few code commits (AFAIK, only 1 commit of
mine in the master branch has anything other than documentation changes)
and be known to be generally sane.
I could be wrong about this; I just know that some people have commit
rights and others do not. I have no idea what the process is for
attaining said rights.
Thanks,
--
~Robert Cochran
GPG Fingerprint - E778 2DD4 FEA6 6A68 6F26 AD2D E5C3 EB36 4886 8871
next prev parent reply other threads:[~2016-09-26 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 4:26 bug#24362: 25.1.50; Inconsistent docstring between pcase-let and pcase-let* Chunyang Xu
2016-09-14 23:06 ` Robert Cochran
2016-09-15 21:36 ` Michael Heerdegen
2016-09-15 21:57 ` Robert Cochran
2016-09-15 22:00 ` Drew Adams
2016-09-15 22:40 ` Michael Heerdegen
2016-09-23 16:26 ` Michael Heerdegen
2016-09-23 20:45 ` Robert Cochran
2016-09-25 14:32 ` Michael Heerdegen
2016-09-26 23:39 ` Robert Cochran [this message]
2019-11-08 3:43 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h992p6xu.fsf@cochranmail.com \
--to=robert-emacs@cochranmail.com \
--cc=24362@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).