git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [DOCBUG] git subtree synopsis needs updating

From
HRHerman van Rink <rink@initfour.nl>
Date
Oct 20, 2012, 19:40 UTC
Message-ID
<5082FE13.2000003@initfour.nl>
In-Reply-To
<20121019152158.4297707b@chalon.bertin.fr>
On 10/19/2012 03:21 PM, Yann Dirson wrote:
Show 21 quoted lines
> 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").
>
The version of subtree in contrib is rather out-dated unfortunately.

I've collected a bunch of patches in https://github.com/helmo/git/tree/subtree-updates

The documentation issue is also fixed in there.
-- 
Met vriendelijke groet / Regards,

Herman van Rink
Initfour websolutions
Previous: Yann DirsonNext: Yann Dirson
Message 2 of 7 in “[DOCBUG] git subtree synopsis needs updating”
  1. Yann DirsonOct 19, 2012
  2. Herman van RinkOct 20, 2012
  3. Yann DirsonOct 24, 2012
  4. greened@obbligato.orgJan 1, 2013
  5. Techlive ZhengJan 19, 2013
  6. greened@obbligato.orgJan 1, 2013
  7. Yann DirsonJan 18, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.