From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] 01/01: * company/company-capf.el: Don't ignore things like semantic-capf.
Date: Sun, 29 Jun 2014 06:05:29 +0300 [thread overview]
Message-ID: <53AF8279.7010809@yandex.ru> (raw)
In-Reply-To: <E1Ww0zZ-0004du-Br@vcs.savannah.gnu.org>
On 06/15/2014 06:20 AM, Stefan Monnier wrote:
> monnier pushed a commit to branch master
> in repository elpa.
>
> commit 69014aa7f585eed4b85b3202146a5c63da58d887
> Author: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sat Jun 14 23:20:16 2014 -0400
>
> * company/company-capf.el: Don't ignore things like semantic-capf.
> ---
> .gitignore | 1 +
> packages/company/company-capf.el | 9 ++++++---
> 2 files changed, 7 insertions(+), 3 deletions(-)
Just a note: if the edit of .gitignore was in a separate commit,
applying this patch to upstream would've been a matter of saving an
email to a file and running one command:
git am -i -c -p3 \[elpa\]\ 01_01\:\ \*\ company_company-capf.el\:\
Don\'t\ ignore\ things\ like\ semantic-capf..eml
As it was, I had to edit out that piece out of the email manually.
The -i flag above is to edit the commit message: with the current format
of notifications, it includes "monnier pushed a commit ..." and the
original commit's headers. It would be nice to figure out a way to omit
them automatically. '-c' doesn't seem to help.
next parent reply other threads:[~2014-06-29 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140615032024.17790.10550@vcs.savannah.gnu.org>
[not found] ` <E1Ww0zZ-0004du-Br@vcs.savannah.gnu.org>
2014-06-29 3:05 ` Dmitry Gutov [this message]
2014-06-29 7:25 ` [elpa] 01/01: * company/company-capf.el: Don't ignore things like semantic-capf Andreas Schwab
2014-06-29 21:32 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53AF8279.7010809@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).