From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Samuel Tardieu <sam@rfc1149.net>, git@vger.kernel.org
Subject: Re: Invalid refspec?
Date: Thu, 20 Mar 2008 09:46:01 -0700 [thread overview]
Message-ID: <7vy78dwdh2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0803200914420.19665@iabervon.org> (Daniel Barkalow's message of "Thu, 20 Mar 2008 09:21:18 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> We need a test for the src being an object name around line 443 in
> remote.c; I'll have something this evening if nobody beats me to it.
Careful. That is ONLY valid for pushes. For fetches, you are allowed to
name existing refs and nothing else.
next prev parent reply other threads:[~2008-03-20 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 10:53 Invalid refspec? Samuel Tardieu
2008-03-20 13:21 ` Daniel Barkalow
2008-03-20 16:46 ` Junio C Hamano [this message]
2008-03-20 17:12 ` Daniel Barkalow
2008-03-20 19:08 ` 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=7vy78dwdh2.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=sam@rfc1149.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).