From: Junio C Hamano <gitster@pobox.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: Aw: Re: [PATCH 1/3] Remove outdated/missleading/irrelevant entries from glossary-content.txt
Date: Tue, 02 Apr 2013 11:26:58 -0700 [thread overview]
Message-ID: <7vy5d0dc0d.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <559824715.741522.1364923497242.JavaMail.ngmail@webmail15.arcor-online.net> (Thomas Ackermann's message of "Tue, 2 Apr 2013 19:24:57 +0200 (CEST)")
Thomas Ackermann <th.acker@arcor.de> writes:
>> Even though I personally am slightly in favor of removal, I suspect
>> that is primarily because I already know what Git tag is, and it is
>> different from the type tag in the Lisp-speak.
>>
> I assumed the cardinality of the set of Lisp users is so small that
> this addition will confuse more people than help somebody.
>
>> The text indeed has a room for improvement, but it probably makes
>> sense to have an entry for `directory` here, as folks who are used
>> to say "Folders" may not know what it is.
>>
> I assumed the number of such people so low that it's not worth
> to keep this - to most people obvious - explanation.
For the above two (they are of the same theme) to help one audience,
I tend to be cautious and try not to say "I don't fall into the
target audience, and to me it is misleading/irrelevant, so let's
remove it".
>> Which one of outdated, misleading or irrelevant category does this
>> fall into? It certainly is not outdated (diff --cc/-c is often a
>> way to view evil merges), the text defines what an evil merge is
>> precisely and I do not think it is misleading. Is it irrelevant?
>>
> I considered it "irrelevant" because it tries to define
> "evil merge" which is - at least to my experience - not used
> as some kind of well known notion. But I might of course be wrong.
In a merge-heavy workflow, evil merges have to happen from time to
time, and it is a good concept to know about.
I however think the description is too literal and it does not lead
to the understanding of what it is used for. I see a few questions
on the stackoverflow with unsatisfactory literal answers, too.
prev parent reply other threads:[~2013-04-02 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 17:24 Aw: Re: [PATCH 1/3] Remove outdated/missleading/irrelevant entries from glossary-content.txt Thomas Ackermann
2013-04-02 18:26 ` Junio C Hamano [this message]
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=7vy5d0dc0d.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=th.acker@arcor.de \
/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).