public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: greened@obbligato•org
To: Yann Dirson <dirson@bertin•fr>
Cc: git list <git@vger•kernel.org>
Subject: Re: [DOCBUG] git subtree synopsis needs updating
Date: Mon, 31 Dec 2012 20:51:41 -0600	[thread overview]
Message-ID: <877gnx39aa.fsf@waller.obbligato.org> (raw)
In-Reply-To: <20121019152158.4297707b@chalon.bertin.fr> (Yann Dirson's message of "Fri, 19 Oct 2012 15:21:58 +0200")

Yann Dirson <dirson@bertin•fr> writes:

> As the examples in git-subtree.txt show, the synopsis in the same file should
> surely get a patch along the lines of:
>
> -'git subtree' add   -P <prefix> <commit>
> +'git subtree' add   -P <prefix> <repository> <commit>
>
> Failure to specify the repository (by just specifying a local commit) fails with
> the cryptic:
>
>  warning: read-tree: emptying the index with no arguments is deprecated; use --empty
>  fatal: just how do you expect me to merge 0 trees?

Specifying a local branch works fine, though, as does a raw commit
hash.  What do you mean by "local commit?"

I have updated the documentation and will submit it tonight or tomorrow.

Any invalid refspec should be caught early and a more useful message
will be displayed.

> Furthermore, the doc paragraph for add, aside from mentionning <repository>, also
> mentions a <refspec> which the synopsis does not show either.

Fixed.

> As a sidenote it someone wants to do some maintainance, using "." as repository when
> the branch to subtree-add is already locally available does not work well either
> (fails with "could not find ref myremote/myhead").

Seems to work for me.  Can you give me the command you're using when you
see the problem?

Thanks for the report!

                          -David

next prev parent reply	other threads:[~2013-01-01  2:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 13:21 [DOCBUG] git subtree synopsis needs updating Yann Dirson
2012-10-20 19:40 ` Herman van Rink
2012-10-24 14:29   ` Yann Dirson
2013-01-01  1:47     ` greened
2013-01-19  5:48   ` Techlive Zheng
2013-01-01  2:51 ` greened [this message]
2013-01-18 14:37   ` Yann Dirson

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=877gnx39aa.fsf@waller.obbligato.org \
    --to=greened@obbligato$(echo .)org \
    --cc=dirson@bertin$(echo .)fr \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox