From: Stephen Kelly <steveire@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: Creating remote branch called HEAD corrupts remote clones
Date: Wed, 27 Apr 2011 13:29:50 +0200 [thread overview]
Message-ID: <BANLkTi=DgXrWZ0ObBYi2mgk-+8w8iXM7VQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinkR+jEKkno30fiHBZ-PMVvvv7FxQ@mail.gmail.com>
On Wed, Apr 27, 2011 at 11:48 AM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> No problems here:
I had another go.
mkdir remote
cd remote/
git init --bare
cd ../
git clone remote/ alice
cd alice/
echo test >> file
git add file
git commit -am w
git push origin master
echo test >> file
git commit -am w
git branch HEAD
git push origin HEAD
git push
cd ..
git clone remote bob
cd bob/
git branch
git pull --rebase
echo test >> file
git commit -am w
git push
git pull
git pull
git pull
echo test >> file
git commit -am w
git push
cd ../alice
git branch
git status
echo test >> file
git commit -am w
git push
echo test2 >> file
git commit -am w
git push
git pull
echo test3 >> file
git commit -am w
git status
git push
gitk
stephen@bishop:/tmp/git$ mkdir remote
stephen@bishop:/tmp/git$ cd remote/
stephen@bishop:/tmp/git/remote$ git init --bare
Initialized empty Git repository in /tmp/git/remote/
stephen@bishop:/tmp/git/remote$ cd ../
stephen@bishop:/tmp/git$ git clone remote/ alice
Cloning into alice...
done.
warning: You appear to have cloned an empty repository.
stephen@bishop:/tmp/git$ cd alice/
stephen@bishop:/tmp/git/alice$ echo test >> file
stephen@bishop:/tmp/git/alice$ git add file
stephen@bishop:/tmp/git/alice$ git commit -am w
[master (root-commit) 072df32] w
1 files changed, 1 insertions(+), 0 deletions(-)
create mode 100644 file
stephen@bishop:/tmp/git/alice{master}$ git push origin master
Counting objects: 3, done.
Writing objects: 100% (3/3), 210 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
To /tmp/git/remote/
* [new branch] master -> master
stephen@bishop:/tmp/git/alice{master}$ echo test >> file
stephen@bishop:/tmp/git/alice{master}$ git commit -am w
[master b39d099] w
1 files changed, 1 insertions(+), 0 deletions(-)
stephen@bishop:/tmp/git/alice{master}$ git branch HEAD
stephen@bishop:/tmp/git/alice{master}$ git push origin HEAD
Counting objects: 5, done.
Writing objects: 100% (3/3), 242 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
To /tmp/git/remote/
* [new branch] HEAD -> HEAD
stephen@bishop:/tmp/git/alice{master}$ git push
Everything up-to-date
stephen@bishop:/tmp/git/alice{master}$ cd ..
stephen@bishop:/tmp/git$ git clone remote bob
Cloning into bob...
done.
stephen@bishop:/tmp/git$ cd bob/
stephen@bishop:/tmp/git/bob{master}$ git pull --rebase
From /tmp/git/remote
072df32..b39d099 HEAD -> origin/HEAD
Current branch master is up to date.
stephen@bishop:/tmp/git/bob{master}$ echo test >> file
stephen@bishop:/tmp/git/bob{master}$ git commit -am w
[master b39d099] w
1 files changed, 1 insertions(+), 0 deletions(-)
stephen@bishop:/tmp/git/bob{master}$ git push
Total 0 (delta 0), reused 0 (delta 0)
To /tmp/git/remote
072df32..b39d099 HEAD -> master
stephen@bishop:/tmp/git/bob{master}$ git pull
Current branch master is up to date.
stephen@bishop:/tmp/git/bob{master}$ git pull
Current branch master is up to date.
stephen@bishop:/tmp/git/bob{master}$ git pull
Current branch master is up to date.
stephen@bishop:/tmp/git/bob{master}$ echo test >> file
stephen@bishop:/tmp/git/bob{master}$ git commit -am w
[master 47699a9] w
1 files changed, 1 insertions(+), 0 deletions(-)
stephen@bishop:/tmp/git/bob{master}$ git push
Counting objects: 5, done.
Writing objects: 100% (3/3), 240 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
To /tmp/git/remote
b39d099..47699a9 HEAD -> master
stephen@bishop:/tmp/git/bob{master}$ cd ../alice
stephen@bishop:/tmp/git/alice{master}$ git branch
HEAD
* master
stephen@bishop:/tmp/git/alice{master}$ git status
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
#
nothing to commit (working directory clean)
stephen@bishop:/tmp/git/alice{master}$ echo test >> file
stephen@bishop:/tmp/git/alice{master}$ git commit -am w
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
[master 7e83bed] w
1 files changed, 1 insertions(+), 0 deletions(-)
stephen@bishop:/tmp/git/alice{master}$ git push
Everything up-to-date
stephen@bishop:/tmp/git/alice{master}$ echo test2 >> file
stephen@bishop:/tmp/git/alice{master}$ git commit -am w
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
[master b4f5b5b] w
1 files changed, 1 insertions(+), 0 deletions(-)
stephen@bishop:/tmp/git/alice{master}$ git push
Everything up-to-date
stephen@bishop:/tmp/git/alice{master}$ git pull
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
remote: Counting objects: 5, done.
remote: Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
From /tmp/git/remote
072df32..47699a9 master -> origin/master
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
First, rewinding head to replay your work on top of it...
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
Applying: w
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
stephen@bishop:/tmp/git/alice{master}$ echo test3 >> file
stephen@bishop:/tmp/git/alice{master}$ git commit -am w
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
[master cc2088e] w
1 files changed, 1 insertions(+), 0 deletions(-)
stephen@bishop:/tmp/git/alice{master}$ git status
warning: refname 'HEAD' is ambiguous.
warning: refname 'HEAD' is ambiguous.
# On branch master
# Your branch is ahead of 'origin/master' by 2 commits.
#
nothing to commit (working directory clean)
stephen@bishop:/tmp/git/alice{master}$ git push
Everything up-to-date
stephen@bishop:/tmp/git/alice{master}$
stephen@bishop:/tmp/git/alice{master}$ git --version
git version 1.7.4.1
next prev parent reply other threads:[~2011-04-27 11:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 10:02 Creating remote branch called HEAD corrupts remote clones Stephen Kelly
2011-01-20 11:14 ` Stephen Kelly
2011-01-20 13:03 ` Thomas Rast
2011-01-20 15:05 ` Stephen Kelly
2011-01-20 15:41 ` Erik Faye-Lund
2011-01-20 16:00 ` Stephen Kelly
2011-01-20 17:32 ` Felipe Contreras
2011-01-20 19:21 ` Wesley J. Landaker
2011-01-20 19:53 ` Junio C Hamano
2011-01-20 20:38 ` Jeff King
2011-01-20 21:43 ` Junio C Hamano
2011-01-20 21:54 ` Jeff King
2011-01-20 23:52 ` Felipe Contreras
2011-01-21 17:37 ` Junio C Hamano
2011-01-22 12:46 ` Felipe Contreras
2011-02-20 13:17 ` Stephen Kelly
2011-04-26 12:09 ` Stephen Kelly
2011-04-26 18:18 ` Felipe Contreras
2011-04-27 9:18 ` Stephen Kelly
2011-04-27 9:48 ` Felipe Contreras
2011-04-27 11:29 ` Stephen Kelly [this message]
2011-04-27 11:32 ` Felipe Contreras
2011-04-27 11:37 ` Stephen Kelly
2011-04-27 12:26 ` Felipe Contreras
2011-04-27 12:21 ` Erik Faye-Lund
2011-04-27 12:49 ` Erik Faye-Lund
2011-05-02 19:26 ` Stephen Kelly
2011-05-02 19:43 ` Erik Faye-Lund
2011-05-03 17:54 ` Felipe Contreras
2011-05-03 18:08 ` Stephen Kelly
2011-05-03 19:20 ` Felipe Contreras
2011-05-04 12:35 ` Erik Faye-Lund
2011-05-09 7:51 ` [PATCH] only warn about ambiguous refs if stderr is a tty Erik Faye-Lund
2011-05-09 8:03 ` Jeff King
2011-05-09 8:41 ` Erik Faye-Lund
2011-05-09 10:32 ` Jeff King
2011-05-09 12:37 ` Erik Faye-Lund
2011-05-09 12:49 ` Jeff King
2011-05-09 16:33 ` Junio C Hamano
2011-05-09 22:09 ` Jeff King
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='BANLkTi=DgXrWZ0ObBYi2mgk-+8w8iXM7VQ@mail.gmail.com' \
--to=steveire@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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).