From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Dan Nicolaescu <dann@ics.uci.edu>, emacs-devel@gnu.org
Subject: Re: VC state
Date: Thu, 10 Apr 2008 15:17:39 -0400 [thread overview]
Message-ID: <jwvwsn5o70t.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <18429.53477.115936.800815@kahikatea.snap.net.nz> (Nick Roberts's message of "Thu, 10 Apr 2008 20:33:41 +1200")
>> > * vc-status doesn't seem to heed vc-stay-local or vc-cvs-stay-local.
>>
>> That is fine, vc-status does not care about those, it just displays
>> whatever the backend tells it to display. The backends are the ones
>> that are supposed to take care of this.
> I don't understand. After vc-dired has gone, how do I find which files under
> version control are modified without consulting the (remote) repository?
> Do you just mean that this functionality is yet to be implemented but when
> it is it won't be done in vc-status?
The way I see it is: `vc-status' should work in "stay-local" mode.
Always. Then we add a `vc-pull' which may contact the
remote repository.
Stefan
next prev parent reply other threads:[~2008-04-10 19:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 5:54 VC state Stefan Monnier
2008-04-06 17:40 ` Dan Nicolaescu
2008-04-07 15:16 ` Stefan Monnier
2008-04-08 15:03 ` conflict state (was Re: VC state) Dan Nicolaescu
2008-04-09 20:35 ` conflict state Stefan Monnier
2008-04-09 21:39 ` Dan Nicolaescu
2008-04-10 0:44 ` Stefan Monnier
2008-04-08 20:45 ` VC state Dan Nicolaescu
2008-04-09 2:44 ` Stefan Monnier
2008-04-09 3:07 ` Dan Nicolaescu
2008-04-09 3:52 ` Nick Roberts
2008-04-09 22:54 ` Dan Nicolaescu
2008-04-10 5:53 ` VC development [was Re: VC state] Nick Roberts
2008-04-10 8:33 ` VC state Nick Roberts
2008-04-10 14:13 ` Dan Nicolaescu
2008-04-11 12:01 ` Nick Roberts
2008-04-10 19:17 ` Stefan Monnier [this message]
2008-04-09 14:02 ` Stefan Monnier
2008-04-10 17:28 ` Dan Nicolaescu
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=jwvwsn5o70t.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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.