git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junio@pobox.com>
Cc: "Matthew Ogilvie" <mmogilvi_git@miniinfo.net>,
	git@vger.kernel.org, "Martin Langhoff" <martin@catalyst.net.nz>,
	"Frank Lichtenheld" <djpig@debian.org>
Subject: Re: [PATCH 0/3] git-cvsserver: Add support for some binary files
Date: Mon, 19 May 2008 10:38:21 +1200	[thread overview]
Message-ID: <46a038f90805181538v56aee5b8y33d68b226a62494f@mail.gmail.com> (raw)
In-Reply-To: <7v7idteqzn.fsf@gitster.siamese.dyndns.org>

On Sat, May 17, 2008 at 12:03 PM, Junio C Hamano <junio@pobox.com> wrote:
> Matthew Ogilvie <mmogilvi_git@miniinfo.net> writes:
>
>> This series of patches extends git-cvsserver to support telling the
>> CVS client to set the -kb (binary) mode for files that git considers
>> to be binary (and not for text files).  It includes updates to
>> documentation and tests.
>
> I am unfortunately not familiar with this part of the system and I'd need
> to summon help from experts, but it looks rather nicely done.

Looks good.

I was at first a bit troubled - "cvsserver doesn't do keyword
expansion anyway" was my first thought - but it makes sense to have
this to help newline-munging clients.

IIRC, one thing that is _not_ handled well in CVS -k flag changes on
the server side (since -k modes are not versioned). If we are
guessing, this may be more likely to happen, or at least more likely
to _surprise_ people.

Matthew, have you had a chance to test k mode changes against clients?
Are we reasonably bug-compatible with the original turd^H^H^Hhing? ;-)

Sorry about the latency!

cheers,



m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

  parent reply	other threads:[~2008-05-18 22:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  4:35 [PATCH 0/3] git-cvsserver: Add support for some binary files Matthew Ogilvie
2008-05-15  4:35 ` [PATCH 1/3] git-cvsserver: add mechanism for managing working tree and current directory Matthew Ogilvie
2008-05-15  4:35   ` [PATCH 2/3] implement gitcvs.usecrlfattr Matthew Ogilvie
2008-05-15  4:35     ` [PATCH 3/3] git-cvsserver: add ability to guess -kb from contents Matthew Ogilvie
2008-05-17  0:03 ` [PATCH 0/3] git-cvsserver: Add support for some binary files Junio C Hamano
2008-05-18 22:10   ` Matthew Ogilvie
2008-05-18 22:38   ` Martin Langhoff [this message]
2008-05-19  7:35     ` Matthew Ogilvie
2008-05-19  9:34       ` Johannes Schindelin
2008-05-20  3:05         ` Matthew Ogilvie
2008-05-19 10:53       ` Martin Langhoff

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=46a038f90805181538v56aee5b8y33d68b226a62494f@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=djpig@debian.org \
    --cc=git@vger.kernel.org \
    --cc=junio@pobox.com \
    --cc=martin@catalyst.net.nz \
    --cc=mmogilvi_git@miniinfo.net \
    /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).