From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jan Wielemaker <wielemak@science.uva.nl>
Cc: git@vger.kernel.org
Subject: Re: git-cvsserver commit trouble BUG+Work-around
Date: Thu, 4 Oct 2007 13:56:00 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710041352480.4174@racer.site> (raw)
In-Reply-To: <46823.146.50.26.20.1191496739.squirrel@webmail.science.uva.nl>
Hi,
On Thu, 4 Oct 2007, Jan Wielemaker wrote:
> Indeed, the trouble is here: git-cvsserver, near line 1203:
>
> my $parenthash = `git show-ref -s refs/heads/$state->{module}`;
>
> $state->{module} is -of course- HEAD. git show-ref -s refs/heads/HEAD
> indeed gives no output. git show-ref -s refs/heads/master works just
> fine.
Ah! Did you do "CVSROOT=:ext:blablub cvs co HEAD"?
You should "co master". The branches in git are the modules in cvs.
HEAD is too volatile, you cannot make a proper module from it (imagine for
example "git checkout next" where "next" is a branch, followed by "git
checkout html", where "html" is another branch).
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-04 12:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 11:48 git-cvsserver commit trouble (unexpected end of file in client) Jan Wielemaker
2007-10-03 13:13 ` Jan Wielemaker
2007-10-03 14:57 ` Jan Wielemaker
2007-10-03 16:11 ` Johannes Schindelin
2007-10-03 18:42 ` Jan Wielemaker
2007-10-03 18:55 ` Johannes Schindelin
[not found] ` <200710032325.55128.wielemak@science.uva.nl>
[not found] ` <Pine.LNX.4.64.0710032311480.28395@racer.site>
2007-10-04 7:27 ` Jan Wielemaker
2007-10-04 11:18 ` git-cvsserver commit trouble BUG+Work-around Jan Wielemaker
2007-10-04 12:56 ` Johannes Schindelin [this message]
2007-10-04 13:06 ` Jan Wielemaker
2007-10-04 15:29 ` [PATCH/RFT] cvsserver: only allow checkout of branches Johannes Schindelin
2007-10-04 16:18 ` Frank Lichtenheld
2007-10-04 16:32 ` Johannes Schindelin
2007-10-04 17:06 ` Jan Wielemaker
2007-10-04 17:18 ` Johannes Schindelin
2007-10-04 18:04 ` Frank Lichtenheld
2007-10-04 21:15 ` Frank Lichtenheld
2007-10-04 21:49 ` Johannes Schindelin
2007-10-04 21:55 ` Shawn O. Pearce
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=Pine.LNX.4.64.0710041352480.4174@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=wielemak@science.uva.nl \
/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).