mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Philip Oakley" <>
To: "anatoly techtonik" <>
Cc: "Ævar Arnfjörð Bjarmason" <>,
	"Randall S. Becker" <>,
	"Junio C Hamano" <>,
	"Git Mailing List" <>,
	"Igor Djordjevic" <>
Subject: Re: Re: Unify annotated and non-annotated tags
Date: Sun, 24 Dec 2017 12:31:36 -0000	[thread overview]
Message-ID: <99FE6DCAB81A4510ACF961290988C094@PhilipOakley> (raw)

From: "anatoly techtonik" <>
> From: Philip Oakley
> > So if I understand correctly, the hope is that `git show-ref --tags` 
> > could
> > get an alternate option `--all-tags` [proper option name required...] 
> > such
> > that the user would not have to develop the rather over the complicated
> > expression that used a newish capability of a different command.
> > Would that be right?

> That's correct.

> > Or at least update the man page docs to clarify the annotated vs
> > non-annotated tags issue (many SO questions!).

> Are there stats how many users read man pages and what is their
> reading session length? I mean docs may not help much,

The "reading the manual" question is fairly well answered in the Human Error 
literature in terms of clarity and effectiveness, and the normal human error 
rates (for interest search for "Panko" "Spreadsheet errors" [1]). Typical 
human error rate is 1%. Most pilot error ends up being, in part, caused by 
confusing / incomplete manuals (i.e. we fail to support them).

If the manuals are the peak of perfection then they are well visited and the 
supporting material is usually good. If manuals are a sprawling upland with 
bogs, fissure, islands of inaccessability, then they are rarely used.

Git does suffer from having a lot of separate commands, which makes seeing 
the woods for the trees difficult sometimes, especially as its core concepts 
are not always well understood.

Improving the manuals (as reference material) will always help, even if the 
trickle down effect is slow (made worse by alternate sources of error - 
Stackoverflow and blogs... ;-)

> > And indicate if the --dereference and/or --hash options would do the 
> > trick!
> > - maybe the "^{}" appended would be part of the problem (and need that 
> > new
> > option "--objectreference" ).

> --dereference would work if it didn't require extra processing.
> It is hard to think about other option name that would give
> desired result.
> ---
> anatoly t.

"This paper reviews human cognition processes and shows first that humans 
cannot be error free no matter how hard they try, and second that our 
intuition about errors and how we can reduce them is based on appallingly 
bad knowledge." 

  reply	other threads:[~2017-12-24 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2017-11-23 15:08 ` Re: Unify annotated and non-annotated tags Randall S. Becker
2017-11-23 21:24   ` Thomas Braun
2017-11-24  9:52   ` anatoly techtonik
2017-11-24 10:24     ` Ævar Arnfjörð Bjarmason
2017-12-02 21:26       ` anatoly techtonik
2017-12-02 22:25         ` Philip Oakley
2017-12-23 13:41           ` anatoly techtonik
2017-12-24 12:31             ` Philip Oakley [this message]
2017-12-03  5:54         ` Junio C Hamano
2017-11-24 14:11     ` Randall S. Becker

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=99FE6DCAB81A4510ACF961290988C094@PhilipOakley \ \ \ \ \ \ \ \

* 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

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).