all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: (elisp) Generic Functions cl-defmethod documentation bug?
Date: Wed, 03 Jan 2018 16:57:29 -0600	[thread overview]
Message-ID: <86o9ma4kkm.fsf@stephe-leake.org> (raw)
In-Reply-To: <83bmicclii.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 02 Jan 2018 17:45:25 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stephen Leake <stephen_leake@stephe-leake.org>
>> Date: Tue, 02 Jan 2018 07:41:19 -0600
>> 
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 
>> >>      ‘STRUCT-TAG’
>> >>           The argument must be an instance of a class named STRUCT-TAG
>> >>           defined with ‘cl-defstruct’ (*note (cl)Structures::), or of
>> >>           one of its parent classes.
>> >>
>> >> Shouldn't 'parent classes' be 'child classes'?
>> >
>> > That sounds right, indeed.  And instead of "tag" it should say "type"
>> > since this is a type and not a tag.
>> 
>> Ok, committed in b6add8c7
>
> Thanks, but why to master?  Documentation patches should be pushed to
> the release branch.

Sorry, I realized that after I committed.

I found instructions for backporting a commit in
admin/notes/git-workflow:

-------------
cd ~/emacs/emacs-26
git cherry-pick -xe b6add8c7...

and add "Backport:" to the commit string.  

git push
-------------

is that the correct process?

-- 
-- Stephe



  reply	other threads:[~2018-01-03 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01 13:37 (elisp) Generic Functions cl-defmethod documentation bug? Stephen Leake
2018-01-02  5:09 ` Stefan Monnier
2018-01-02 13:41   ` Stephen Leake
2018-01-02 15:45     ` Eli Zaretskii
2018-01-03 22:57       ` Stephen Leake [this message]
2018-01-04  3:36         ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86o9ma4kkm.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.