From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Yann Dirson" <dirson@bertin.fr>,
"Santi Béjar" <santi@agolina.net>,
git@vger.kernel.org
Subject: Re: [PATCH 0/4] Re: Undocumented git-diff syntax
Date: Mon, 11 Oct 2010 22:56:34 +0200 [thread overview]
Message-ID: <AANLkTinJBmmZirkM5a9UEOamvJEC_iuPFcNUXZUvv9qO@mail.gmail.com> (raw)
In-Reply-To: <20101011160224.GA25842@burratino>
Heya,
On Mon, Oct 11, 2010 at 18:02, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Patch 5 gives --no-index its own prominent mention in the DESCRIPTION
> section. I suspect that is a bad idea --- too much to learn for new
> users --- and that the description should go under OPTIONS, but I ran
> out of time.
Well, that answers my question in [1/5], *mutters at gmail's lack of a
tree view*.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-10-11 20:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 13:03 Undocumented git-diff syntax Yann Dirson
2010-10-11 13:59 ` Santi Béjar
2010-10-11 14:17 ` Yann Dirson
2010-10-11 14:52 ` Santi Béjar
2010-10-11 16:02 ` [PATCH 0/4] " Jonathan Nieder
2010-10-11 16:03 ` [PATCH 1/5] Documentation: gitrevisions is in section 7 Jonathan Nieder
2010-10-11 20:49 ` Sverre Rabbelier
2010-10-11 16:04 ` [PATCH 2/4] Documentation: diff can compare blobs Jonathan Nieder
2010-10-11 16:05 ` [PATCH 3/4] Documentation: expand 'git diff' SEE ALSO section Jonathan Nieder
2010-10-11 16:06 ` [PATCH 4/4] Documentation: update "git diff --no-index" description Jonathan Nieder
2010-10-11 16:07 ` [RFC/PATCH 5/4] Documentation: flesh out diff --no-index description Jonathan Nieder
2010-10-13 22:40 ` Junio C Hamano
2010-10-11 18:52 ` [PATCH 0/4] Re: Undocumented git-diff syntax Yann Dirson
2010-10-11 20:56 ` Sverre Rabbelier [this message]
2010-10-11 16:57 ` Jakub Narebski
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTinJBmmZirkM5a9UEOamvJEC_iuPFcNUXZUvv9qO@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=dirson@bertin.fr \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=santi@agolina.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).