# [JGIT] Pushing the HEAD ref?

2 messages from 2009-03-17 to 2009-03-17. Participants: Daniel Cheng, Shawn O. Pearce.
Thread: https://gitlist.dev/t/18337

## Daniel Cheng, 2009-03-17 04:04

Subject: [JGIT] Pushing the HEAD ref?
Message-ID: <ff6a9c820903162104v2ca62437ua3da6bafba3ea101@mail.gmail.com>
URL: https://gitlist.dev/e/ff6a9c820903162104v2ca62437ua3da6bafba3ea101%40mail.gmail.com

```
Hi List,

When I develop the freenet transport, I found the refWriter in
WalkPushConnection never write the HEAD refs, even if this is a new
repository.
Is this the expected behaviour? This cause error when I clone the repository.

Regards,
Daniel Cheng.

```

## Shawn O. Pearce, 2009-03-17 14:28

Subject: Re: [JGIT] Pushing the HEAD ref?
Message-ID: <20090317142835.GB20222@spearce.org>
URL: https://gitlist.dev/e/20090317142835.GB20222%40spearce.org
In-Reply-To: <ff6a9c820903162104v2ca62437ua3da6bafba3ea101@mail.gmail.com>

```
Daniel Cheng <j16sdiz+freenet@gmail.com> wrote:
> 
> When I develop the freenet transport, I found the refWriter in
> WalkPushConnection never write the HEAD refs, even if this is a new
> repository.
> Is this the expected behaviour? This cause error when I clone the repository.

Nope.

Check WalkPushConnection's createNewRepository().  The method is
called from line 162 where we try to create a new HEAD symbolic
ref to one of the refs/heads/$name being pushed, and we also put
a tiny config file.  This way a repository pushed over sftp://
is a valid repository if you later get shell access to it.

Sounds like you didn't push a refs/heads/$name when you created
the repository, or you something is broken in this section.

-- 
Shawn.

```
