git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Peter Shenkin <shenkin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clarify that '--tags' fetches tags only
Date: Fri, 30 Sep 2011 11:37:51 -0700	[thread overview]
Message-ID: <7vwrcpoozk.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <loom.20110930T041939-332@post.gmane.org> (Peter Shenkin's message of "Fri, 30 Sep 2011 02:51:21 +0000 (UTC)")

Peter Shenkin <shenkin@gmail.com> writes:

> Perhaps it will be useful to say what would have been most
> helpful for me. In the current documentation for "fetch
> --tags", one sentence reads, "This flag lets all tags and
> their associated  objects be downloaded." The following small
> modification would, IMO, be sufficient: "This flag causes all
> tags and their associated objects (only) to be downloaded."

Hmm, from time to time we seem to see this kind of documentation
suggestion where:

 - We (try to) describe what xyzzy does by saying "This is what xyzzy
   does". We specifically do not say "In addition to what normally
   happens, xyzzy causes these additional things to happen."

 - The reader (somehow) assumes xyzzy does more than what we described in
   the documentation, even we did not say "In addition to..."; and then

 - A patch is proposed to add "these other things are _not_ done", after
   existing "This is what xyzzy does".

And it is not limited to the description of this particular option.

I think in general our documentation aims to spell out _all_ that happens,
and explicitly say "In addition to what normally happens", "This page
lists only the most common ways", etc., when such a clatification is
needed.

I am wondering if there is a systemic failure that gives an impression
that by default the documentation is incomplete and all other unspecified
thing also happens to the readers? If so are there things that we could
do better without going through individual description?

  parent reply	other threads:[~2011-09-30 18:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02 21:04 [PATCH] Clarify that '--tags' fetches tags only Anatol Pomozov
2011-09-02 21:18 ` Drew Northup
2011-09-21 23:52 ` Anatol Pomozov
2011-09-22  0:13   ` Michael Witten
2011-09-22  0:49     ` Junio C Hamano
2011-09-22  2:01       ` Michael Witten
2011-09-22  2:07         ` Michael Witten
2011-09-22  3:13           ` Andrew Ardill
2011-09-22  3:24             ` Michael Witten
2011-09-22  3:39               ` [PATCH] Docs: Clarify the --tags option of `git fetch' Michael Witten
2011-09-22  3:48                 ` Michael Witten
2011-09-22  4:28               ` [PATCH] Clarify that '--tags' fetches tags only Junio C Hamano
2011-09-22  7:23                 ` [PATCH v3] Docs: Clarify the --tags option of `git fetch' Michael Witten
2011-09-22 17:10                   ` Junio C Hamano
2011-09-22 17:35                     ` Michael Witten
2011-09-22 17:38                       ` Michael Witten
2011-09-22  4:00         ` [PATCH] Clarify that '--tags' fetches tags only Junio C Hamano
2011-09-22  4:17           ` [PATCH v2] Docs: Clarify the --tags option of `git fetch' Michael Witten
2011-09-22  1:14   ` [PATCH] Clarify that '--tags' fetches tags only Daniel Johnson
2011-09-30  2:51     ` Peter Shenkin
2011-09-30  8:44       ` Jakub Narebski
2011-09-30 13:23       ` Michael Witten
2011-10-01  5:40         ` Peter Shenkin
2011-10-01 14:11           ` Michael Witten
2011-10-01 17:16             ` Peter Shenkin
2011-10-01 18:45               ` Michael Witten
2011-10-01 20:22                 ` Peter Shenkin
2011-10-01 20:56                   ` Michael Witten
2011-10-01 21:41                     ` Peter Shenkin
2011-10-01 22:06                       ` Peter Shenkin
2011-09-30 18:37       ` Junio C Hamano [this message]
2011-10-01  5:51         ` Peter Shenkin

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=7vwrcpoozk.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=shenkin@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.
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).