unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Dan Nicolaescu <dann@gnu.org>
Cc: Eric James Michael Ritz <Eric@cybersprocket.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: [vc-git] Showing ‘.git/*’ files in vc-dir
Date: Thu, 01 Jul 2010 18:25:50 +0200	[thread overview]
Message-ID: <4C2CC18E.8080901@swipnet.se> (raw)
In-Reply-To: <yxqwrtffck6.fsf@fencepost.gnu.org>



Dan Nicolaescu skrev 2010-07-01 17.26:
> Jan Djärv<jan.h.d@swipnet.se>  writes:
>
>>
>> FWIW, I think vc-dir should be similar to the command line in this
>> respect, i.e. just commit if there are unregistered files present.
>> After all, it is not a limitation of the underlying version control
>> system.
>
> vc-dir does not care, it just uses C-x v v
> For 'unregistered files C-x v v says that the next action is vc-register
> For 'edited files C-x v v says that the next action is vc-checkin
> Hence it can't do both...

I'm not familiar with the inner workings of vc, so when I say vc-dir I really 
mean vc as a whole.  Anyway, what you say is of course correct, but if there 
are both edited and unregistered, C-x v v in this case should say vc-checkin. 
  After all, commit is far more common than register.

	Jan D.



  reply	other threads:[~2010-07-01 16:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 18:29 [vc-git] Showing ‘.git/*’ files in vc-dir Eric James Michael Ritz
2010-06-29 19:54 ` Dan Nicolaescu
2010-06-29 20:07   ` Eric James Michael Ritz
2010-06-29 20:54     ` Dan Nicolaescu
2010-06-29 21:16       ` Eric James Michael Ritz
2010-07-01  1:27       ` Stefan Monnier
2010-07-01  3:06         ` Dan Nicolaescu
2010-07-01  5:47           ` Miles Bader
2010-07-01  6:44             ` Dan Nicolaescu
2010-07-01 13:40               ` Eric James Michael Ritz
2010-07-04 17:26               ` Eric James Michael Ritz
2010-07-04 19:30                 ` Dan Nicolaescu
2010-07-04 19:45                   ` Eric James Michael Ritz
2010-07-04 17:27               ` Stefan Monnier
2010-07-04 19:26                 ` Dan Nicolaescu
2010-07-01  7:36           ` Jan Djärv
2010-07-01  8:32             ` Dan Nicolaescu
2010-07-01  8:39               ` Glenn Morris
2010-07-01  9:29                 ` Jan Djärv
2010-07-01 15:34                 ` Dan Nicolaescu
2010-07-01  9:23               ` Jan Djärv
2010-07-01 15:26                 ` Dan Nicolaescu
2010-07-01 16:25                   ` Jan Djärv [this message]
2010-07-23 15:30                     ` Stefan Monnier
2010-07-01  8:35             ` Glenn Morris
2010-07-01  9:16               ` Miles Bader
2010-07-01  9:22                 ` Deniz Dogan
2010-07-01 15:23                 ` Dan Nicolaescu
2010-07-01 21:14                 ` Glenn Morris
2010-07-01 22:24                   ` René Kyllingstad
2010-07-02  3:14                     ` Miles Bader

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=4C2CC18E.8080901@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=Eric@cybersprocket.com \
    --cc=dann@gnu.org \
    --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).