From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git.txt: command re-classification
Date: Fri, 19 Jan 2007 17:59:20 -0500 [thread overview]
Message-ID: <20070119225920.GA26442@fieldses.org> (raw)
In-Reply-To: <eoriau$n97$1@sea.gmane.org>
On Fri, Jan 19, 2007 at 11:57:12PM +0100, Jakub Narebski wrote:
> Nicolas Pitre wrote:
>
> > Also, having:
> >
> > git-am(1)
> > Apply a series of patches from a mailbox.
> >
> > git-applymbox(1)
> > Apply a series of patches in a mailbox.
> >
> > looks a bit weird. Why two commands with almost the same description?
> > Maybe one of them could be relegated to ancillary? Or even both of them
> > to foreignscminterface?
>
> Because they are almost the same (same command, different interface).
> git-applymbox is legacy for Linus.
Given how often this question is asked, maybe git-aplymbox should just
be removed from this and every other global list of commands. Linus
(and whoever else is used to it) knows where to find it.
Unless there's really something it has that git-am doesn't.
--b.
next prev parent reply other threads:[~2007-01-19 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 22:25 [PATCH] Documentation: revisit command qualification in git.txt Nicolas Pitre
2007-01-19 6:32 ` [PATCH] Documentation/git.txt: command re-classification Junio C Hamano
2007-01-19 22:08 ` Nicolas Pitre
2007-01-19 22:18 ` Jakub Narebski
2007-01-19 22:22 ` Junio C Hamano
2007-01-19 22:44 ` Nicolas Pitre
2007-01-19 22:57 ` Jakub Narebski
2007-01-19 22:59 ` J. Bruce Fields [this message]
2007-01-19 23:36 ` Junio C Hamano
2007-01-20 1:44 ` Nicolas Pitre
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=20070119225920.GA26442@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=jnareb@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 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).