From: Andreas Schwab <schwab@suse.de>
To: "Göktuğ Kayaalp" <self@gkayaalp.com>
Cc: 24082@debbugs.gnu.org, jca@wxcvbn.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#24082: 25.1; vc-dir for CVS repositories list all files as if from toplevel directory
Date: Tue, 11 Oct 2016 09:51:29 +0200 [thread overview]
Message-ID: <mvmd1j7uxvi.fsf@hawking.suse.de> (raw)
In-Reply-To: <87shs3y6tx.fsf@xi.bootis> ("Göktuğ Kayaalp"'s message of "Tue, 11 Oct 2016 05:09:46 +0300")
On Okt 11 2016, Göktuğ Kayaalp <self@gkayaalp.com> wrote:
> On 2016-10-11 02:55 +0300, Dmitry Gutov <dgutov@yandex.ru> wrote:
>> On 09.10.2016 15:18, Göktuğ Kayaalp wrote:
>>
>>> Does not show unregistered files at all, so need to add them from shell.
>>> In fact, ‘cvs status’ command itself does not know anything about
>>> unregistered files at all, it only deals with registered files.
>>
>> For some reason, I get 'cvs -f status' include the unregistered files in
>> the output with the remote repo, but not with the one I've created from
>> your test scenario. With the remote one, the output looks like:
>>
>> cvs -f status
>> ? asdasd
>> ? tests/foo
>> [... snip ...]
>> Commit Identifier: 6fOuIAy2oJtoJf6y
>> [... snip ...]
>
> This looks like a CVSNT server[1] (given the ‘commit identifier’), so
Commit identifiers are also implemented in CVS.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2016-10-11 7:51 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 [this message]
2016-10-11 8:51 ` Dmitry Gutov
2016-10-11 15:48 ` Göktuğ Kayaalp
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=mvmd1j7uxvi.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=24082@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=jca@wxcvbn.org \
--cc=self@gkayaalp.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 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).