From: Dmitry Gutov <dgutov@yandex.ru>
To: Eric Abrahamsen <eric@ericabrahamsen.net>, help-gnu-emacs@gnu.org
Subject: Re: single-command git commits
Date: Tue, 19 Jul 2016 03:54:29 +0300 [thread overview]
Message-ID: <3acc43ba-daa0-48db-25fb-f06cfcc98cb4@yandex.ru> (raw)
In-Reply-To: <87a8he8nj5.fsf@ericabrahamsen.net>
On 07/19/2016 03:44 AM, Eric Abrahamsen wrote:
> I'd like to use the highest-level vc function
> available to me,
vc-git-checkin?
> ideally something above the level of git-awareness!
(vc-call-backend backend 'checkin files comment)
next prev parent reply other threads:[~2016-07-19 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1664.1468886830.26859.help-gnu-emacs@gnu.org>
2016-07-19 0:33 ` single-command git commits Emanuel Berg
2016-07-19 0:44 ` Eric Abrahamsen
2016-07-19 0:54 ` Dmitry Gutov [this message]
2016-07-19 1:02 ` Eric Abrahamsen
[not found] ` <mailman.1667.1468889678.26859.help-gnu-emacs@gnu.org>
2016-07-19 1:04 ` Emanuel Berg
[not found] ` <mailman.1666.1468889079.26859.help-gnu-emacs@gnu.org>
2016-07-19 1:00 ` Emanuel Berg
2016-07-19 0:06 Eric Abrahamsen
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=3acc43ba-daa0-48db-25fb-f06cfcc98cb4@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@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.
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).