git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 15:28:02 -0700	[thread overview]
Message-ID: <7v4pb6gv7x.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47DD9890.3060005@gnu.org> (Paolo Bonzini's message of "Sun, 16 Mar 2008 23:00:48 +0100")

Paolo Bonzini <bonzini@gnu.org> writes:

> Junio C Hamano wrote:
>> 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?
>
> It was before too.  The problem arises if one found the problem,
> deleted the symlink, added the regular file -- and now cvsserver stops
> working at all. :-(

I fully agree that "stops working at all" was baaaaad, and your patch may
be an improvement.

What I am questioning is what the code should do (IOW, what would be good
for cvs clients to see).  Should it send a symlink as a regular file, or
simply just omit it?  If the answer is "the former", then we do not have
to worry about it any further after applying your patch.  Otherwise we
still have to do something _else_ after applying your patch.  I did not
know which way we would want to proceed, and I still don't.

  reply	other threads:[~2008-03-16 22:28 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
2008-03-16 22:00   ` Paolo Bonzini
2008-03-16 22:28     ` Junio C Hamano [this message]
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=7v4pb6gv7x.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).