From: Andreas Ericsson <ae@op5.se>
To: Andreas Ericsson <ae@op5.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Remote 'master' not updated, but works somehow
Date: Thu, 07 Dec 2006 12:35:06 +0100 [thread overview]
Message-ID: <4577FC6A.9050707@op5.se> (raw)
In-Reply-To: <4577FBAB.4070802@op5.se>
scratch this. I just noticed I had somehow managed to get the directory
setup like this:
devel:softpub/mkpub.git <-- a real repo
devel:softpub/mkpub.git/.git <-- the repo that got pushed to
Andreas Ericsson wrote:
> Having for a long time been thoroughly annoyed by our strict umasks, I
> decided to write a little program to deal with it, and naturally I put
> it in a git repo. After the initial commit
> (c0fa1db09bad112f7271378d907bf33d74c06f6b) I published it to my git
> space on our development server and cloned it out again (to get the
> nifty remotes things set up for free).
>
> Then I noticed I had rushed it, as I usually do with hacks involving a
> total of less than 200 lines of code, so I had to make a couple of more
> commits to make it work.
>
> After having pushed the fixes to the public site I went to have a look
> at it in gitweb, at https://devel.op5.se/~exon/git/
>
> I was quite surprised to find that 'master' was still pointing to the
> root commit. After the usual culprits were excluded (permissions, bad
> paths, whatnot), I decided to try to clone the repo again to a different
> location.
>
> Here's what happened:
>
> devel!exon:~$ git clone softpub/mkpub.git/ mkpub
> remote: Generating pack...
> remote: Done counting 17 objects.
> remote: Deltifying 17 objects.
> remote: 100% (17/17) done
> Indexing 17 objects.
> remote: Total 17 (delta 3), reused 0 (delta 0)
> 100% (17/17) done
> Resolving 3 deltas.
>
> devel!exon:~$ cat softpub/mkpub.git/refs/heads/master
> c0fa1db09bad112f7271378d907bf33d74c06f6b
> devel!exon:~$ cat mkpub/.git/refs/heads/master
> 5ba01a4709bcc8b482b207ba91d78ddb689a4091
> devel!exon:~$ cd mkpub/
> devel!exon:~/mkpub$ git push
> Everything up-to-date
> devel!exon:~/mkpub$ git rev-list master
> 5ba01a4709bcc8b482b207ba91d78ddb689a4091
> e6a80831737517aa7ef29628429a18935b71de1d
> 8926e1519f69d95685ab5252886e7b237e21108e
> c0bfedaf572ee550af7927acb89a1a2e01c1ef2c
> c0fa1db09bad112f7271378d907bf33d74c06f6b
> devel!exon:~/mkpub$ GIT_DIR=../softpub/mkpub.git/ git rev-list master
> c0fa1db09bad112f7271378d907bf33d74c06f6b
>
> (yes, the repo only has 4 commits)
>
> And that's where I am now. Note that *cloning* from the repo actually
> works, although I can't for the life of me figure out why.
>
> Any thoughts?
>
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
next prev parent reply other threads:[~2006-12-07 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 11:31 Remote 'master' not updated, but works somehow Andreas Ericsson
2006-12-07 11:35 ` Andreas Ericsson [this message]
2006-12-07 11:49 ` Shawn 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=4577FC6A.9050707@op5.se \
--to=ae@op5.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.