From: Yann Dirson <dirson@bertin.fr>
To: git list <git@vger.kernel.org>
Subject: [DOCBUG] git subtree synopsis needs updating
Date: Fri, 19 Oct 2012 15:21:58 +0200 [thread overview]
Message-ID: <20121019152158.4297707b@chalon.bertin.fr> (raw)
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?
Furthermore, the doc paragraph for add, aside from mentionning <repository>, also
mentions a <refspec> which the synopsis does not show either.
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").
--
Yann Dirson - Bertin Technologies
next reply other threads:[~2012-10-19 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 13:21 Yann Dirson [this message]
2012-10-20 19:40 ` [DOCBUG] git subtree synopsis needs updating 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
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=20121019152158.4297707b@chalon.bertin.fr \
--to=dirson@bertin.fr \
--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).