[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A problem with old bugs

From: Thien-Thi Nguyen
Subject: Re: A problem with old bugs
Date: Thu, 02 Mar 2017 08:38:56 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

() Marcin Borkowski <address@hidden>
() 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 -


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

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]