login
Header Space

 
 

Re: Meaning of "fatal: protocol error: bad line length character"?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Shawn O. Pearce <spearce@...>
Cc: Bill Lear <rael@...>, <git@...>
Date: Monday, January 22, 2007 - 4:15 pm

"Shawn O. Pearce" <spearce@spearce.org> writes:


It turns out that this was a stupidity on the part of the tester
(i.e. me).

I let the distro to install a version of git in /usr/bin/, and
my .cshrc is not set up to add /home/junio/git-active/bin (I
have $HOME/git-{master,next,pu,maint}/bin and git-active is a
symlink to git-master right now -- usually it points at
git-next), for non-interactive session like invoking
receive-pack.  But my bash startup does.  The breakage I was
seeing was _NOT_ because of differences between tcsh and bash,
but because the fix is fairly recent.

I forced the master version of receive-pack to be used on the
remote side using --receive-pack command line parameter, and
things seem to work fine with either tcsh or bash.

So, no, there might be valid reasons to hate tcsh, but this is
not one of them.


-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Meaning of "fatal: protocol error: bad line length chara..., Junio C Hamano, (Mon Jan 22, 4:15 pm)
speck-geostationary