unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: A problem with old bugs
Date: Thu, 02 Mar 2017 08:38:56 +0100	[thread overview]
Message-ID: <87wpc8b01b.fsf@zigzag.favinet> (raw)
In-Reply-To: <87poi19ldj.fsf@jane> (Marcin Borkowski's message of "Wed, 01 Mar 2017 14:28:40 +0100")

[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]


() Marcin Borkowski <mbork@mbork.pl>
() Wed, 01 Mar 2017 14:28:40 +0100

   Nope.  What do I do to get them?

I'm not familiar w/ full details these days, but i think
generally you need to ask the maintainer for them, in the
process making some convincing arguments that you will not
besmirch Emacs and GNU (by introducing or advocating non-Free
software, for example), and that your interaction w/ the project
will be a net positive.  Once swayed, the maintainer starts the
paperwork process (which might involve snail mail), and If All
Goes Well, you will be notified one day.

Another way is to fork Emacs, or find a way to get write privs
on an existing fork.  That resolves the write privs issue, but
raises coordination/synchronization issues.  I was about to say
"not recommended", but on second thought, hey why not?  I can
imagine inter-repo hacking being fruitful and fun, too (YMMV).

   > What are you waiting for?

   Nobody gave them to me.

   What should be the workflow once I have them?  I assume that
   I branch off fresh master, push my branch and write here -
   correct?

See file CONTRIBUTE.

-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)
   (pcase (context query)
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2017-03-02  7:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  8:22 A problem with old bugs Marcin Borkowski
2017-03-01 10:26 ` Thien-Thi Nguyen
2017-03-01 13:28   ` Marcin Borkowski
2017-03-02  7:38     ` Thien-Thi Nguyen [this message]
2017-03-02 12:33       ` Noam Postavsky
2017-03-02 16:53         ` Richard Stallman
2017-03-07  6:17         ` Marcin Borkowski
2017-03-06 13:19     ` Phillip Lord
2017-03-07  6:16       ` Marcin Borkowski
2017-03-07 12:24         ` Phillip Lord
2017-03-01 16:16 ` Eli Zaretskii
2017-03-07  6:15   ` Marcin Borkowski
2017-03-07 16:51     ` Eli Zaretskii
2017-03-08  7:01       ` Marcin Borkowski
2017-03-08 16:08         ` Eli Zaretskii
2017-05-21 16:00 ` John Wiegley

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=87wpc8b01b.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=emacs-devel@gnu.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.
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).