All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Stefanus Du Toit <sjdutoit@gmail.com>
Cc: git@vger.kernel.org, John Keeping <john@keeping.me.uk>,
	"David A. Greene" <greened@obbligato.org>
Subject: Re: git-subtree manpage missing from git-manpages tarballs
Date: Sun, 8 Dec 2013 14:30:21 -0800	[thread overview]
Message-ID: <20131208223020.GB9108@google.com> (raw)
In-Reply-To: <CABGRy0o3AJLMhmVJL8XAjrnQJd=yuV+1Q=cLToetnhmB0V=hfA@mail.gmail.com>

Hi,

Stefanus Du Toit wrote:

> The git-subtree manpage is currently missing from the git-manpages
> tarballs at https://code.google.com/p/git-core/.
>
> For example, https://code.google.com/p/git-core/downloads/detail?name=git-manpages-1.8.5.1.tar.gz
> does not include it.
>
> A side effect of this is that "git help subtree" fails when using git
> installed from homebrew, because the homebrew recipe uses those
> tarballs as its source of documentation.

git-subtree and its documentation are in the contrib/subtree
directory.  contrib/subtree/Makefile includes rules to build
a manpage for it.

If the homebrew rules are installing the git-subtree command
from there, perhaps they could be tweaked to build the manpage,
too.  What do you think?

Alternatively: I'm not sure what the status of git-subtree
maintenance is.  Is there someone taking active enough care
of it that it would make sense to promote it out of contrib/
to be a full git command installed by default?

Thanks,
Jonathan

  reply	other threads:[~2013-12-08 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 16:14 git-subtree manpage missing from git-manpages tarballs Stefanus Du Toit
2013-12-08 22:30 ` Jonathan Nieder [this message]
2013-12-09  0:40   ` Stefanus Du Toit

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=20131208223020.GB9108@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=greened@obbligato.org \
    --cc=john@keeping.me.uk \
    --cc=sjdutoit@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.