[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: VC state
From: |
Dan Nicolaescu |
Subject: |
Re: VC state |
Date: |
Thu, 10 Apr 2008 07:13:39 -0700 |
Nick Roberts <address@hidden> writes:
> > > * 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?
Exactly. This is similar to what vc-dired does. The backends are
responsible for the information that vc-status displays.
If you actually care about such functionality you might want to
volunteer to implement, it's pretty low on the priority list...
- Re: conflict state, (continued)
- Re: VC state, Dan Nicolaescu, 2008/04/08
- Re: VC state, Stefan Monnier, 2008/04/08
- Re: VC state, Dan Nicolaescu, 2008/04/08
- Re: VC state, Nick Roberts, 2008/04/08
- Re: VC state, Dan Nicolaescu, 2008/04/09
- VC development [was Re: VC state], Nick Roberts, 2008/04/10
- Re: VC state, Nick Roberts, 2008/04/10
- Re: VC state,
Dan Nicolaescu <=
- Re: VC state, Nick Roberts, 2008/04/11
- Re: VC state, Stefan Monnier, 2008/04/10
- Re: VC state, Stefan Monnier, 2008/04/09
- Re: VC state, Dan Nicolaescu, 2008/04/10