From: Carlos Pita <carlosjosepita@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 19696@debbugs.gnu.org, Fabian Ezequiel Gallina <galli.87@gmail.com>
Subject: bug#19696: Acknowledgement (24.4; python.el: blank line eldoc error)
Date: Wed, 4 Feb 2015 16:47:46 -0300 [thread overview]
Message-ID: <CAELgYhdw9GiaKsEyQkTXBZ+XLjTPW4u-42BwNKwMpy-0r85_OQ@mail.gmail.com> (raw)
In-Reply-To: <jwvk2zx79po.fsf-monnier+emacsbugs@gnu.org>
> OK, thanks. I know that Fabián has worked on master's python.el using
> an older version of Emacs (at some point in the past at least), so maybe
Btw, now that we're on that subject. What would you advise to keep
things in sync? Specifically, I want to work on master so I clone it
and add a new online remote, say in gitlab/github/bitbucket, to keep
my local repos (home, work, laptop) in touch. The problem is the repo
is huge, so I make a shallow clone and some cleanup, and this indeed
ameliorates the size issue. The repo passes from huge to just big. But
still, I'm just working on one or two files at the time being... so
eventually I ended up deciding to only pull python.el and avoid the
full repo approach. I don't want to post noisy reports as this one but
it's difficult when you're not a fulltime emacs developer.
next prev parent reply other threads:[~2015-02-04 19:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 17:32 bug#19696: 24.4; python.el: blank line eldoc error Carlos Pita
[not found] ` <handler.19696.B.14222935664090.ack@debbugs.gnu.org>
2015-02-03 23:23 ` bug#19696: Acknowledgement (24.4; python.el: blank line eldoc error) Carlos Pita
2015-02-04 15:25 ` Stefan Monnier
2015-02-04 18:01 ` Carlos Pita
2015-02-04 18:11 ` Carlos Pita
2015-02-04 18:35 ` Stefan Monnier
2015-02-04 18:43 ` Carlos Pita
2015-02-04 18:59 ` Carlos Pita
2015-02-04 19:34 ` Stefan Monnier
2015-02-04 19:47 ` Carlos Pita [this message]
2015-02-04 22:38 ` Fabián Ezequiel Gallina
2015-02-05 2:47 ` Stefan Monnier
2015-02-05 9:09 ` Fabián Ezequiel Gallina
2015-02-09 15:56 ` bug#19696: python.el: blank line eldoc error Carlos Pita
2015-02-10 2:54 ` Fabián Ezequiel Gallina
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=CAELgYhdw9GiaKsEyQkTXBZ+XLjTPW4u-42BwNKwMpy-0r85_OQ@mail.gmail.com \
--to=carlosjosepita@gmail.com \
--cc=19696@debbugs.gnu.org \
--cc=galli.87@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.