From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Todd Zullinger <tmz@pobox.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: categorization, documentation and packaging of "git core" commands
Date: Wed, 7 Feb 2018 13:09:55 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1802071308250.9047@localhost.localdomain> (raw)
In-Reply-To: <20180207172902.GL1427@zaya.teonanacatl.net>
On Wed, 7 Feb 2018, Todd Zullinger wrote:
> Robert P. J. Day wrote:
> > first, here are the executables under /usr/libexec/git-core/ that
> > are unreferenced by that web page, but that should be fine as
> > almost all of them would be considered underlying helpers or
> > utilities (except for things like git-subtree, but we're still
> > unclear on its status, right?):
>
> I don't think there's anything unclear about git subtree's status.
> It's in contrib/ within the source, so it's not part of the core git
> suite. Some distributions (Fedora being one of them) ship a
> git-subtree package to provide it for users who want it.
not true, "git-subtree" is part of fedora's lowest-level
"git-core" package.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2018-02-07 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 13:18 categorization, documentation and packaging of "git core" commands Robert P. J. Day
2018-02-07 17:29 ` Todd Zullinger
2018-02-07 18:09 ` Robert P. J. Day [this message]
2018-02-07 18:42 ` Todd Zullinger
2018-02-07 20:03 ` Robert P. J. Day
2018-02-07 20:14 ` Jeff King
2018-02-07 20:38 ` Robert P. J. Day
2018-02-07 21:18 ` Todd Zullinger
2018-02-09 13:51 ` Robert P. J. Day
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=alpine.LFD.2.21.1802071308250.9047@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=tmz@pobox.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 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).