git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andrew Clausen <clausen@econ.upenn.edu>
To: git@vger.kernel.org
Subject: [PATCH] helpful error message when send-pack finds no refs in common.
Date: Tue, 16 Oct 2007 17:31:39 -0400	[thread overview]
Message-ID: <20071016213139.GF13454@econ.upenn.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

Hi all,

Please cc me, I'm not subscribed.

git-push fails when pushing into an empty repository if you don't specify
a branch:

	git --bare init some-repo

	git-push some-repo

To get this to work, you need to do

	git-push some-repo master

I attached a patch so that the error message suggests trying the latter.

Cheers,
Andrew


[-- Attachment #2: 0001-helpful-error-message-when-send-pack-finds-no-refs-i.patch --]
[-- Type: text/plain, Size: 820 bytes --]

>From ee888ea1a7d2e75a0439569e36eabe4620e8f833 Mon Sep 17 00:00:00 2001
Date: Tue, 16 Oct 2007 17:16:05 -0400
Subject: [PATCH] helpful error message when send-pack finds no refs in common.
Signed-off-by: Andrew Clausen <clausen@econ.upenn.edu>

---
 send-pack.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/send-pack.c b/send-pack.c
index f74e66a..f0b0825 100644
--- a/send-pack.c
+++ b/send-pack.c
@@ -204,7 +204,8 @@ static int send_pack(int in, int out, struct remote *remote, int nr_refspec, cha
 		return -1;
 
 	if (!remote_refs) {
-		fprintf(stderr, "No refs in common and none specified; doing nothing.\n");
+		fprintf(stderr,
+			"No refs in common and none specified; doing nothing.\n"			"Perhaps you should specify a branch such as 'master'.\n");
 		return 0;
 	}
 
-- 
1.5.3.1


                 reply	other threads:[~2007-10-16 22:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071016213139.GF13454@econ.upenn.edu \
    --to=clausen@econ.upenn.edu \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).