From: Chris Shoemaker <c.shoemaker@cox.net>
To: git@vger.kernel.org
Cc: skimo@liacs.nl
Subject: Re: git and gitweb inconsistencies
Date: Sun, 23 Oct 2005 13:30:55 -0400 [thread overview]
Message-ID: <20051023173055.GA3019@pe.Belkin> (raw)
In-Reply-To: <20051023115939.GG8383MdfPADPa@greensroom.kotnet.org>
On Sun, Oct 23, 2005 at 01:59:39PM +0200, Sven Verdoolaege wrote:
> On Sat, Oct 22, 2005 at 08:14:12PM -0400, Chris Shoemaker wrote:
> > A few days later, I ran git-cvsimport again, with -i. This imported
> > just the recent changes, but the view from gitweb didn't change. :(
>
> Are you sure you didn't just create a new import *inside* the old import ?
> Do you have, say, both an 'objects' and a '.git/objects' directory ?
OH! You, sir, DO have a crystal ball. :)
I foolishly assumed that the second time I ran git-cvsimport, with -C
/pub/scm/project/ it would be able to detect that I was using the
stand-alone GIT-DIR. But, it obviously didn't. I guess the solution
is use specify GIT_DIR everytime I run git-cvstimport.
So, it seems that git-web.cgi detects and prefers the stand-alone
directory structure, because I specify it in the projects_list file,
while git-cat-file, and git-update-ref default to using .git.
>
> > $ echo `git-rev-list tip --max-count=1` > refs/heads/mytest
> > $ git-cat-file -t `cat refs/heads/mytest`
>
> That should be
>
> git-update-ref refs/heads/mytest tip
> (the new head will appear in .git/refs/heads/mytest,
> unless you've set GIT_DIR)
> git-cat-file -t mytest
Ah, and if I'd used that command, I would have realized something was
wrong when mytest *didn't* appear in refs/heads, but rather
.git/refs/heads.
Thanks for thinking creatively about how I could have messed it up!
-chris
>
>
> skimo
next prev parent reply other threads:[~2005-10-23 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 0:14 git and gitweb inconsistencies Chris Shoemaker
2005-10-23 11:59 ` Sven Verdoolaege
2005-10-23 17:30 ` Chris Shoemaker [this message]
2005-10-23 18:28 ` Sven Verdoolaege
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=20051023173055.GA3019@pe.Belkin \
--to=c.shoemaker@cox.net \
--cc=git@vger.kernel.org \
--cc=skimo@liacs.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).