From: Junio C Hamano <gitster@pobox.com>
To: greened@obbligato.org
Cc: Drew Crawford <drew@drewcrawfordapps.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git subtree error (just how do you expect me to merge 0 trees?)
Date: Mon, 31 Dec 2012 21:54:01 -0800 [thread overview]
Message-ID: <7vy5gdbg92.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <87d2xpwnty.fsf@waller.obbligato.org> (greened@obbligato.org's message of "Mon, 31 Dec 2012 22:04:41 -0600")
greened@obbligato.org writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>>> With one positional option, git-subtree add simply assumes
>>> it's a refspec. Is there an easy way to check whether a string is a
>>> proper refspec? Even better would be a way to check if a string is a
>>> path to a git repository.
>>
>> Do you literally mean "a path to a repository" in the above, or do
>> you mean "a remote that is like what is accepted by 'git fetch'"?
>
> It's the latter as git-subtree calls git-fetch to do the work of
> getting revisions.
If that is the case, t should behave similar to 'git fetch' for
consistency. If you want to name "current repository", you can
simply give "." as the repository parameter; this has long been
supported by 'git fetch' (as 'git pull . $branch' has been the way
to say 'git merge' for a long time).
next prev parent reply other threads:[~2013-01-01 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 23:04 git subtree error (just how do you expect me to merge 0 trees?) Drew Crawford
2013-01-01 1:44 ` greened
2013-01-01 2:09 ` greened
2013-01-01 3:16 ` Junio C Hamano
2013-01-01 4:04 ` greened
2013-01-01 5:54 ` Junio C Hamano [this message]
2013-01-01 2:39 ` greened
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=7vy5gdbg92.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=drew@drewcrawfordapps.com \
--cc=git@vger.kernel.org \
--cc=greened@obbligato.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.
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).