From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 41684@debbugs.gnu.org
Subject: bug#41684: [PATCH] Highlight typed variables in python
Date: Sat, 13 Jun 2020 12:21:28 +0300 [thread overview]
Message-ID: <da789fccce0dc81893b81f964cc23ef85ca50d80.camel@yandex.ru> (raw)
In-Reply-To: <83blln4999.fsf@gnu.org>
On Sat, 2020-06-13 at 12:15 +0300, Eli Zaretskii wrote:
> > From: Konstantin Kharlamov <hi-angel@yandex.ru>
> > Cc: 41684-done@debbugs.gnu.org
> > Date: Sat, 13 Jun 2020 11:57:44 +0300
> >
> > > . it is better to submit patches in "git format-patch" format,
> > > as
> > > that makes it easier to apply the patch
> >
> > Hmm, okay… The patch was sent with git-send-email command, is it
> > different from git-format-patch?
>
> It isn't how you send the patches that's the issue, it's the way you
> produced the patch. AFAIK, git-send-email accepts patches formatted
> with git-format-patch, but it doesn't look like you used the latter
> to
> produce a patch.
Thanks, right, I haven't used any other command except git-send-email.
Specifically, I have executed `git send-email -1 --annotate` and then
filled in required fields.
next prev parent reply other threads:[~2020-06-13 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 11:51 bug#41684: [PATCH] Highlight typed variables in python Konstantin Kharlamov
2020-06-09 23:12 ` Konstantin Kharlamov
2020-06-13 7:35 ` Eli Zaretskii
2020-06-13 8:57 ` Konstantin Kharlamov
2020-06-13 9:15 ` Eli Zaretskii
2020-06-13 9:21 ` Konstantin Kharlamov [this message]
2020-06-13 10:44 ` Basil L. Contovounesios
2020-06-13 20:01 ` Andrii Kolomoiets
2020-06-13 20:40 ` Konstantin Kharlamov
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=da789fccce0dc81893b81f964cc23ef85ca50d80.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=41684@debbugs.gnu.org \
--cc=eliz@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.