all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nordlöw <per.nordlow@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Checking vc-state recursively under a directory
Date: Wed, 23 Jul 2008 06:30:08 -0700 (PDT)	[thread overview]
Message-ID: <0e75864d-6e18-45e5-93d5-73757209b817@x35g2000hsb.googlegroups.com> (raw)
In-Reply-To: mailman.15267.1216818264.18990.help-gnu-emacs@gnu.org

On 23 Juli, 15:03, Nikolaj Schumacher <n_schumac...@web.de> wrote:
> Nordlöw <per.nord...@gmail.com> wrote:
> > Is it somehow possible to check whether all the files under a version-
> > controlled directory are all up-to-date (updated)? That is like vc-
> > state() but recursively for a directory?
>
> What do you mean?  up-to-date or updated?  up-to-date means
> (not (vc-workfile-unchanged-p "file")), while updated means something like
> (file-newer-than-file-p "file.elc" "file.el")

I mean like vc-state but for a whole repository, say vc-dir-state(DIR)
and should be behave something like the following (using CVS as
example):
A function that runs "cvs update" and return, say 'up-to-date, if no
file in repository was changed otherwise say 'patched.
If this function returns 'patched we know that something was changed
and we need to rebuild things...

/Nordlöw


  parent reply	other threads:[~2008-07-23 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 10:16 Checking vc-state recursively under a directory Nordlöw
2008-07-23 13:03 ` Nikolaj Schumacher
     [not found] ` <mailman.15267.1216818264.18990.help-gnu-emacs@gnu.org>
2008-07-23 13:30   ` Nordlöw [this message]
2008-07-23 14:00     ` Nikolaj Schumacher
     [not found]     ` <mailman.15274.1216821649.18990.help-gnu-emacs@gnu.org>
2008-07-28 19:31       ` Colin S. Miller
2008-07-23 13:39   ` Nordlöw
2008-07-25 18:59 ` Thr4wn

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=0e75864d-6e18-45e5-93d5-73757209b817@x35g2000hsb.googlegroups.com \
    --to=per.nordlow@gmail.com \
    --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.
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.