git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: greened@obbligato.org
To: Drew Crawford <drew@drewcrawfordapps.com>
Cc: "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 19:44:18 -0600	[thread overview]
Message-ID: <87wqvx3cel.fsf@waller.obbligato.org> (raw)
In-Reply-To: <FBE22FDC-5800-40C8-9778-82DFD27579F6@drewcrawfordapps.com> (Drew Crawford's message of "Thu, 18 Oct 2012 18:04:57 -0500")

Drew Crawford <drew@drewcrawfordapps.com> writes:

> I noticed today that if you leave off the branch name from git subtree like so:
>
> $ git subtree add --prefix somewhere -m "adding CDH as subtree" path/to/repo
> warning: read-tree: emptying the index with no arguments is deprecated; use --empty
> fatal: just how do you expect me to merge 0 trees?
>
> The error message is not particularly helpful (and seems to actually be in read-subtree?)  The solution in my case was to add the branch name on the end of the command.
>
> Ideally it would be better to emit an error-message from a script higher up the calling chain that would be more descriptive about the problem (such as suggesting no branch is specified).--

Good idea.  I'll code it up.

                        -David

  reply	other threads:[~2013-01-01  1:45 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 [this message]
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
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=87wqvx3cel.fsf@waller.obbligato.org \
    --to=greened@obbligato.org \
    --cc=drew@drewcrawfordapps.com \
    --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.
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).