[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs contributions, C and Lisp
From: |
Phillip Lord |
Subject: |
Re: Emacs contributions, C and Lisp |
Date: |
Wed, 19 Feb 2014 16:43:54 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
>> > What red tape? Emacs is about the most red-tape-less project as you
>> > can find, as far as the procedure of admitting a patch is considered.
>>
>>
>> This is an interesting difference of opinion and is probably worth
>> exploring; it's worth knowing what the difficulties where.
>
> That's why I asked what kind of red tape was being alluded to here.
My apologies I had taken it as a rhetorical question.
>> It might also be writing this up -- is there a description anywhere of
>> "how to submit a change to Emacs", and should it not be in the elisp
>> manual?
>
> There's nothing to describe, IMO. If you don't have write access,
> just post the changes and ask for review or approval; if you do have
> write access, you just commit.
Well, you just did just describe it, and it's a very nice, short and
succient description.
>> Incidentally, I say "change" and not "patch". Submitting a change these
>> days generally means "clone, branch, pull request".
>
> Sorry, I don't understand the subtlety.
Sending patches is quite slow and generally painful. This can be quite
an impediment to "drive-by" fixes. Consider (my sole) contribution to
biopython:
commit a85cb7b546a7a3928a578ed05170581c0365c438
Author: Phillip Lord <address@hidden>
Date: Mon Sep 30 17:00:13 2013 +0100
Fix to the English of a section title.
Modified Doc/Tutorial.tex
diff --git a/Doc/Tutorial.tex b/Doc/Tutorial.tex
index dc1d0a3..f46007d 100644
--- a/Doc/Tutorial.tex
+++ b/Doc/Tutorial.tex
@@ -1380,7 +1380,7 @@ used in sequencing work hold quality scores but they
\emph{never} contain a
sequence -- instead there is a partner FASTA file which \emph{does} have the
sequence.
-\section{Working with directly strings}
+\section{Working with strings directly}
\label{sec:seq-module-functions}
To close this chapter, for those you who \emph{really} don't want to use the
sequence
objects (or who prefer a functional programming style to an object orientated
one),
Only doable when the effort is very small.
Phil
- Re: Emacs contributions, C and Lisp (was: Re: /srv/bzr/emacs/trunk r101338: ...), (continued)
- Re: Emacs contributions, C and Lisp (was: Re: /srv/bzr/emacs/trunk r101338: ...), Jorgen Schaefer, 2014/02/17
- Re: Emacs contributions, C and Lisp (was: Re: /srv/bzr/emacs/trunk r101338: ...), Eli Zaretskii, 2014/02/17
- Re: Emacs contributions, C and Lisp, Phillip Lord, 2014/02/18
- Re: Emacs contributions, C and Lisp, Eli Zaretskii, 2014/02/18
- Re: Emacs contributions, C and Lisp, David Kastrup, 2014/02/18
- Re: Emacs contributions, C and Lisp, chad, 2014/02/18
- Re: Emacs contributions, C and Lisp, Eli Zaretskii, 2014/02/18
- Re: Emacs contributions, C and Lisp, chad, 2014/02/19
- Re: Emacs contributions, C and Lisp, Eli Zaretskii, 2014/02/19
- Re: Emacs contributions, C and Lisp, Phillip Lord, 2014/02/19
- Re: Emacs contributions, C and Lisp,
Phillip Lord <=
- Re: Emacs contributions, C and Lisp, Eli Zaretskii, 2014/02/19
- Re: Emacs contributions, C and Lisp, Glenn Morris, 2014/02/18
- Re: Emacs contributions, C and Lisp, Phillip Lord, 2014/02/19
- Re: Emacs contributions, C and Lisp, Glenn Morris, 2014/02/19
- Re: Emacs contributions, C and Lisp, Phillip Lord, 2014/02/20
- Re: Emacs contributions, C and Lisp (was: Re: /srv/bzr/emacs/trunk r101338: ...), Jorgen Schaefer, 2014/02/19
- Re: Emacs contributions, C and Lisp, Thien-Thi Nguyen, 2014/02/19
- Re: Emacs contributions, C and Lisp, David Kastrup, 2014/02/19
- Re: Emacs contributions, C and Lisp, Phillip Lord, 2014/02/19
- Re: Emacs contributions, C and Lisp, David Kastrup, 2014/02/19