From: Dan Nicolaescu <dann@gnu.org>
To: "Göktuğ Kayaalp" <self@gkayaalp.com>
Cc: 24082@debbugs.gnu.org, jca@wxcvbn.org, dgutov@yandex.ru
Subject: bug#24082: [PATCH] Use ‘cvs update’ instead ‘cvs status’ for CVS *vc-dir* buffers
Date: Fri, 21 Oct 2016 21:34:23 -0400 [thread overview]
Message-ID: <yxqeg39np40.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87shs02k7i.fsf@xi.bootis> ("Göktuğ Kayaalp"'s message of "Thu, 13 Oct 2016 21:10:57 +0300")
Göktuğ Kayaalp <self@gkayaalp.com> writes:
> Hello,
>
> What do you think about the patch? Should it be merged?
Sorry, I haven't used CVS in many years, so I don't know the
implications of the proposed changes...
--Dan
> Also, on this thread [1, 2], there's Jérémie's issue which I couldn't
> reproduce (I tried various local and remote repos, including the OpenBSD
> ‘src/’ repo). Do you have any ideas regarding this?
>
> I'll be able to work on the patch in the weekend (GMT+3) if any
> modifications are needed.
>
> -gk.
>
> [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24082#45
> [2] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24082#54
>
> --
> İ. V. Göktuğ Kayaalp <http://www.gkayaalp.com>
> PGP pubkey: <http://www.gkayaalp.com/pubkey.asc>
next prev parent reply other threads:[~2016-10-22 1:34 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 [this message]
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
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=yxqeg39np40.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--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).