unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Göktuğ Kayaalp" <self@gkayaalp.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: schwab@suse.de, 24082@debbugs.gnu.org, jca@wxcvbn.org
Subject: bug#24082: 25.1; vc-dir for CVS repositories list all files as if from toplevel directory
Date: Tue, 11 Oct 2016 18:48:09 +0300	[thread overview]
Message-ID: <87vawy3n0m.fsf@xi.bootis> (raw)
In-Reply-To: <7cb3fd58-618a-1454-10b1-827616cdcbcd@yandex.ru> (message from Dmitry Gutov on Tue, 11 Oct 2016 11:51:25 +0300)

On 2016-10-11 11:51 +0300, Dmitry Gutov <dgutov@yandex.ru> wrote:
> [... snip ...] But if the feature doesn't work with all popular CVS 
> servers, then it would be half-broken anyway, and we'd be better off 
> relying on your solution.

Turns out my cvs was a year behind the latest, and the commitid was
ported in a later release (see also Andreas Schwab's message).  Sorry.

> 'cvs -fnq update' gives:
> [... snip ...]
> (So it doesn't mention up-to-date files; which can be a boon 
> performance-wise, starting with repos of certain size).

‘cvs status’ output is mostly garbage (i.e. not needed) in this context,
whereas every byte of ‘cvs -fnq update’ is used.  Also, the amount of
the output from the latter is a fraction of that from the former.  With
‘status’, reporting even a completely pristine repo will be slow if it
has more than a dozen files, and the results will depend on the CVS
version, regarding unregistered files, commitid, etc.

I'm CC'ing Andreas too, maybe he can comment about Jérémie's issue?
Also, AFAIK we havent heard from Dan Nicolescu yet.

-- 
İ. V. Göktuğ Kayaalp                           <http://www.gkayaalp.com>
                        PGP pubkey: <http://www.gkayaalp.com/pubkey.asc>





  reply	other threads:[~2016-10-11 15:48 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 20:02 bug#24082: 25.1; vc-dir for CVS repositories list all files as if from toplevel directory Göktuğ Kayaalp
2016-07-30  0:35 ` bug#24082: vc-dir changes working directory (git backend) Steve Revilak
2016-10-06 23:32   ` Dmitry Gutov
2016-08-28 20:17 ` bug#24082: [PATCH] Use ‘cvs update’ instead ‘cvs status’ for CVS *vc-dir* buffers Göktuğ Kayaalp
2016-10-06 23:25   ` Dmitry Gutov
2016-10-07 19:29     ` Göktuğ Kayaalp
2016-10-08  1:01       ` Dmitry Gutov
2016-10-08  1:04       ` Dmitry Gutov
2016-10-12  0:59         ` Dan Nicolaescu
2016-10-13 18:10           ` Göktuğ Kayaalp
2016-10-22  1:34             ` Dan Nicolaescu
2016-10-05 18:31 ` bug#24082: Update Göktuğ Kayaalp
2016-10-05 18:33   ` Eli Zaretskii
2016-10-07 14:45 ` bug#24082: 25.1; vc-dir for CVS repositories list all files as if from toplevel directory Jérémie Courrèges-Anglas
2016-10-08  0:38   ` Dmitry Gutov
2016-10-08 15:13     ` Jérémie Courrèges-Anglas
2016-10-08 20:06       ` Dmitry Gutov
2016-10-09 12:18         ` Göktuğ Kayaalp
2016-10-10 23:55           ` Dmitry Gutov
2016-10-11  2:09             ` Göktuğ Kayaalp
2016-10-11  7:51               ` Andreas Schwab
2016-10-11  8:51               ` Dmitry Gutov
2016-10-11 15:48                 ` Göktuğ Kayaalp [this message]
2016-10-10 16:41 ` Jérémie Courrèges-Anglas
2016-10-13 18:47   ` Göktuğ Kayaalp
2016-10-14 20:33     ` Jérémie Courrèges-Anglas
2016-10-15 12:36       ` Dmitry Gutov
2016-10-15 13:20         ` Göktuğ Kayaalp
2016-10-15 14:06           ` Jérémie Courrèges-Anglas
2016-10-15 17:26             ` Göktuğ Kayaalp
2016-10-15 21:36             ` Dmitry Gutov
2016-10-16  0:03               ` Göktuğ Kayaalp
2016-10-16 12:38                 ` Jérémie Courrèges-Anglas
2016-10-16 14:07                   ` Dmitry Gutov
2016-10-16 14:23                     ` Eli Zaretskii
2016-10-16 15:58                       ` Dmitry Gutov
2016-10-16 17:58                         ` Eli Zaretskii
2016-10-18  0:04                           ` Dmitry Gutov
2016-10-18 17:35                             ` Göktuğ Kayaalp

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=87vawy3n0m.fsf@xi.bootis \
    --to=self@gkayaalp.com \
    --cc=24082@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=jca@wxcvbn.org \
    --cc=schwab@suse.de \
    /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).