From: Junio C Hamano <gitster@pobox.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: git@vger.kernel.org, beuc@gnu.org
Subject: Re: [PATCH] git-cvsserver: handle change type T
Date: Sun, 16 Mar 2008 14:21:24 -0700 [thread overview]
Message-ID: <7v63vmicvf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <E1Jay7s-0000dO-IX@fencepost.gnu.org> (Paolo Bonzini's message of "Sun, 16 Mar 2008 20:00:21 +0100")
Paolo Bonzini <bonzini@gnu.org> writes:
> git-cvsserver does not support changes of type T (file type change,
> e.g. symlink->real file). This patch treats them the same as changes
> of type M.
Hmm.
Do cvs clients even know how to handle symlinks, or will this patch just
start sending the readlink(2) result as if it is just a regular file
contents?
next prev parent reply other threads:[~2008-03-16 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 19:00 [PATCH] git-cvsserver: handle change type T Paolo Bonzini
2008-03-16 21:21 ` Junio C Hamano [this message]
2008-03-16 22:00 ` Paolo Bonzini
2008-03-16 22:28 ` Junio C Hamano
2008-03-17 7:54 ` Paolo Bonzini
2008-03-17 8:01 ` Junio C Hamano
2008-03-17 19:34 ` Martin Langhoff
2008-03-17 19:47 ` Paolo Bonzini
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=7v63vmicvf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=beuc@gnu.org \
--cc=bonzini@gnu.org \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).