emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#32999: closed (27.0.50; Typo in Elisp Reference)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#32999: closed (27.0.50; Typo in Elisp Reference)
Date: Wed, 10 Oct 2018 03:32:01 +0000

Your message dated Wed, 10 Oct 2018 06:31:33 +0300
with message-id <address@hidden>
and subject line Re: bug#32999: 27.0.50; Typo in Elisp Reference
has caused the debbugs.gnu.org bug report #32999,
regarding 27.0.50; Typo in Elisp Reference
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
32999: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32999
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 27.0.50; Typo in Elisp Reference Date: Tue, 9 Oct 2018 19:28:54 -0300
Hello.

I found a typo in 'timerp' documentation.  Since it is a trivial fix,
I decided to give the process of sending a patch a try.

I hope everything is according to Emacs Guidelines, but please correct
me if I missed something.

Attachment: 0001-Fix-typo-in-timerp-documentation.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#32999: 27.0.50; Typo in Elisp Reference Date: Wed, 10 Oct 2018 06:31:33 +0300
> From: Mauro Aranda <address@hidden>
> Date: Tue, 9 Oct 2018 19:28:54 -0300
> 
> I found a typo in 'timerp' documentation.  Since it is a trivial fix,
> I decided to give the process of sending a patch a try.
> 
> I hope everything is according to Emacs Guidelines, but please correct
> me if I missed something.

Thanks, pushed to the emacs-26 branch.

> * doc/lispref/os.texi (Timers): Fix typo in 'timerp' documentation.

In the future, please mention the bug number, if known, in the commit
log message, and also include the Copyright-paperwork-exempt: header
if you didn't assign copyright for your contributions.  (If you are
interested, I can send you the assignment form, so that we will be
able to accept your contributions without size limitations.)


--- End Message ---

reply via email to

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