git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: <git@vger.kernel.org>
Subject: [PATCH 4/4] server info: Add HEAD to info/refs
Date: Fri, 27 Apr 2007 04:06:08 +0200	[thread overview]
Message-ID: <20070427020608.22991.29273.stgit@rover> (raw)
In-Reply-To: <20070427020601.22991.13792.stgit@rover>

For some reason, HEAD was not listed in info/refs until now, which means
that git-ls-remote does not return it for dumb transports while the native
transports show it. It would be nice to have it because of git-mirror and
possibly other nifty stuff.

Signed-off-by: Petr Baudis <pasky@suse.cz>
---

 server-info.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/server-info.c b/server-info.c
index f9be5a7..6cddb11 100644
--- a/server-info.c
+++ b/server-info.c
@@ -36,6 +36,7 @@ static int update_info_refs(int force)
 	info_ref_fp = fopen(path1, "w");
 	if (!info_ref_fp)
 		return error("unable to update %s", path0);
+	head_ref(add_info_ref, NULL);
 	for_each_ref(add_info_ref, NULL);
 	fclose(info_ref_fp);
 	rename(path1, path0);

  parent reply	other threads:[~2007-04-27  2:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27  2:06 [PATCH 1/4] Git.pm: config_boolean() -> config_bool() Petr Baudis
2007-04-27  2:06 ` [PATCH 2/4] Git.pm: Add remote_refs() git-ls-remote frontend Petr Baudis
2007-04-27  2:06 ` [PATCH 3/4] [PATCH] git-mirror - exactly mirror another repository Petr Baudis
2007-04-27  4:39   ` Shawn O. Pearce
2007-04-27  2:06 ` Petr Baudis [this message]
2007-04-27  3:51   ` [PATCH 4/4] server info: Add HEAD to info/refs Junio C Hamano
2007-04-27  4:28     ` Petr Baudis
2007-04-27  4:36       ` Junio C Hamano
2007-04-28  6:27 ` [PATCH 1/4] Git.pm: config_boolean() -> config_bool() Junio C Hamano
2007-05-09 10:49   ` [PATCH] " Petr Baudis
2007-05-09 15:13     ` Petr Baudis
2007-05-10  2:12       ` Junio C Hamano
2007-05-09 15:24     ` Junio C Hamano

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=20070427020608.22991.29273.stgit@rover \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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).