From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, Juri Linkov <juri@linkov.net>
Subject: Re: [PATCH] Allow hiding stashes from vc-dir
Date: Fri, 18 Oct 2019 10:39:21 +0200 [thread overview]
Message-ID: <m25zkmsb0m.fsf@gmail.com> (raw)
In-Reply-To: <87ftjqlp7w.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 18 Oct 2019 05:14:27 +0200")
>>>>> On Fri, 18 Oct 2019 05:14:27 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
>> +(declare-function cl-subseq "cl-extra" (seq start &optional end))
Lars> This functions is ;;;###autoload in cl-extra.el, so I would have thought
Lars> that this wouldn't be necessary...
I thought so too, but:
ELC vc/vc-git.elc
In end of data:
vc/vc-git.el:1780:1:Warning: the function ‘cl-subseq’ might not be defined at
runtime.
next prev parent reply other threads:[~2019-10-18 8:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 12:48 [PATCH] Allow hiding stashes from vc-dir Robert Pluim
2019-10-15 12:54 ` Lars Ingebrigtsen
2019-10-15 13:06 ` Eli Zaretskii
2019-10-15 14:02 ` Robert Pluim
2019-10-15 16:19 ` Eli Zaretskii
2019-10-15 18:09 ` Juri Linkov
2019-10-16 1:28 ` Lars Ingebrigtsen
2019-10-16 8:57 ` Robert Pluim
2019-10-17 16:26 ` Robert Pluim
2019-10-18 3:14 ` Lars Ingebrigtsen
2019-10-18 8:39 ` Robert Pluim [this message]
2019-10-18 9:01 ` Eli Zaretskii
2019-10-18 9:25 ` Robert Pluim
2019-10-18 9:31 ` Eli Zaretskii
2019-10-18 10:18 ` Robert Pluim
2019-10-18 12:22 ` Eli Zaretskii
2019-10-18 13:43 ` Robert Pluim
2019-10-19 3:19 ` Stefan Monnier
2019-10-21 9:38 ` Robert Pluim
2019-10-19 8:18 ` Andreas Schwab
2019-10-18 13:22 ` Stefan Monnier
2019-10-18 14:07 ` Robert Pluim
2019-10-19 3:16 ` Stefan Monnier
2019-10-19 8:15 ` Lars Ingebrigtsen
2019-10-21 9:38 ` Robert Pluim
2019-10-15 14:40 ` Michael Albinus
2019-10-15 16:25 ` Eli Zaretskii
2019-10-16 10:18 ` Michael Albinus
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=m25zkmsb0m.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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.