all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Omar Polo <op@omarpolo.com>
Cc: 61577-done@debbugs.gnu.org
Subject: bug#61577: 30.0.50; project-try-vc missing vc-got
Date: Sat, 18 Feb 2023 15:17:37 +0200	[thread overview]
Message-ID: <20c435f7-5e85-c80d-98b5-cdb059986f1f@yandex.ru> (raw)
In-Reply-To: <33K7WG12CN39M.2BL8XP3YCDT9O@venera>

On 18/02/2023 12:48, Omar Polo wrote:

>> Originally, I figured all major backends should be covered, but it won't
>> hurt to add one more, especially since vc-got is in ELPA.
> 
> I guess that now the (require 'vc-svn) could go away too.

Ah yeah, thanks for the suggestion.

> Thanks!
> 
> P.S.: thanks also for the explanation about CVS/RCS/SCCS/SRC.  To be
> fair I never used the project-* functions in a CVS checkout before
> yesterday, and it makes sense not to include them by default.  Well,
> maaaybe a vc-cvs-root that walks up until the root of the checkout
> could be provided, but I'm not too knowledgable about CVS and my usage
> of it is scarce enough that I didn't feel the reason to have it.
> Hardly used anything other than C-x v = in CVS checkouts.

Given that CVS is both unable to provide a faster file listing, and 
(IIUC) its file ignore settings are spread between the directories, a 
user might as well add a new element to project-find-functions, to get 
the basic features. And closer integration will require more work.





      reply	other threads:[~2023-02-18 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 16:56 bug#61577: 30.0.50; project-try-vc missing vc-got Omar Polo
2023-02-17 17:34 ` Omar Polo
2023-02-17 23:27   ` Dmitry Gutov
2023-02-17 23:11 ` Dmitry Gutov
2023-02-18 10:48   ` Omar Polo
2023-02-18 13:17     ` Dmitry Gutov [this message]

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=20c435f7-5e85-c80d-98b5-cdb059986f1f@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=61577-done@debbugs.gnu.org \
    --cc=op@omarpolo.com \
    /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.