* mercurial: commit -m "logmsg" command line: Emacs command
@ 2015-10-15 7:03 Uwe Brauer
2015-10-15 9:21 ` Dmitry Gutov
0 siblings, 1 reply; 2+ messages in thread
From: Uwe Brauer @ 2015-10-15 7:03 UTC (permalink / raw)
To: emacs-devel
Hello
Coming from RCS, I thought that
vc-next-action in a file under HG control, it would be equivalent to run
hg commit -m "logmsg"
From the command line. However it is not.
I tested it several times. I modify 2 files, but run vc-next-action only
in one of them. Hg status tells me the second is modified. When I push
to bitbucket only the one I run vc-next-action is pushed.
Is there any comment I did not try out? What do I miss?
Thanks
Uwe Brauer
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: mercurial: commit -m "logmsg" command line: Emacs command
2015-10-15 7:03 mercurial: commit -m "logmsg" command line: Emacs command Uwe Brauer
@ 2015-10-15 9:21 ` Dmitry Gutov
0 siblings, 0 replies; 2+ messages in thread
From: Dmitry Gutov @ 2015-10-15 9:21 UTC (permalink / raw)
To: emacs-devel
On 10/15/2015 10:03 AM, Uwe Brauer wrote:
> I tested it several times. I modify 2 files, but run vc-next-action only
> in one of them. Hg status tells me the second is modified. When I push
> to bitbucket only the one I run vc-next-action is pushed.
I believe it tries to behave in line with all other VC backends, and
commit only the changes in the marked files (or the current file, in
this example).
> Is there any comment I did not try out? What do I miss?
You should try M-x vc-dir, mark both files, and commit.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-10-15 9:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-15 7:03 mercurial: commit -m "logmsg" command line: Emacs command Uwe Brauer
2015-10-15 9:21 ` Dmitry Gutov
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).