All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: "Ville Skyttä" <ville.skytta@iki.fi>, git@vger.kernel.org
Subject: Re: [PATCH] Spelling fixes
Date: Wed, 10 Aug 2016 09:55:54 -0700	[thread overview]
Message-ID: <xmqq7fbo7ecl.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <f4f313a0-749d-4db2-3afc-9e93ea2ba130@kdbg.org> (Johannes Sixt's message of "Wed, 10 Aug 2016 15:26:54 +0200")

Johannes Sixt <j6t@kdbg.org> writes:

> Am 09.08.2016 um 20:19 schrieb Junio C Hamano:
>>     <BAD>                     <CORRECTED>
>> 
>>     accidently                accidentally
>>     commited                  committed
>>     dependancy                dependency
>>     emtpy                     empty
>>     existance                 existence
>>     explicitely               explicitly
>>     git-upload-achive         git-upload-archive
>>     hierachy                  hierarchy
>>     intial                    initial
>>     mulitple                  multiple
>>     non-existant              non-existent
>>     precendence.              precedence.
>>     priviledged               privileged
>>     programatically           programmatically
>>     psuedo-binary             pseudo-binary
>>     soemwhere                 somewhere
>>     successfull               successful
>>     unkown                    unknown
>>     usefull                   useful
>>     writting                  writing
>
> This reminds me of one occurrence of "indegee" in commit-slab.h that
> should be "indegree". The word is not in this list above, so I don't
> know whether you would like to have it fixed in the same patch or not...
>
> (BTW, is that word "in-degree" or "ingredient"?)

IIRC it is the former, to count "how many incoming arcs does this
node have?"

Will queue to squash in.  Thanks.

> -- Hannes
>
> diff --git a/commit-slab.h b/commit-slab.h
> --- a/commit-slab.h
> +++ b/commit-slab.h
> @@ -8,7 +8,7 @@
>   *
>   * After including this header file, using:
>   *
> - * define_commit_slab(indegee, int);
> + * define_commit_slab(indegree, int);
>   *
>   * will let you call the following functions:
>   *

  reply	other threads:[~2016-08-10 18:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09  8:53 [PATCH] Spelling fixes Ville Skyttä
2016-08-09 18:19 ` Junio C Hamano
2016-08-09 18:41   ` Ville Skyttä
2016-08-10 16:59     ` Junio C Hamano
2016-08-10 13:26   ` Johannes Sixt
2016-08-10 16:55     ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-07  9:34 Ville Skyttä
2018-02-15 15:52 ` Pablo Neira Ayuso
2017-12-07 14:57 Rob Herring
2017-06-25 10:20 Ville Skyttä
2017-06-27 17:35 ` Junio C Hamano
2014-11-15 20:41 Ville Skyttä
2014-11-16 11:40 ` Benno Schulenberg
2014-11-16 11:57   ` Sami Kerola
2014-11-18 13:00 ` Karel Zak
2014-05-14 15:18 Stephen Hemminger
     [not found] ` <20140514081815.04fb8fd0-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-05-14 15:30   ` Richardson, Bruce
2013-12-15 12:19 Ville Skyttä
2013-12-16 19:20 ` Randy Dunlap
2013-12-16 22:00   ` Jeff Kirsher
2014-01-27  1:00 ` Ben Hutchings
2013-02-23 14:31 Ville Skyttä
2013-02-23 14:58 ` Duy Nguyen
2013-02-23 18:23 ` René Scharfe
2013-02-25  6:34   ` Junio C Hamano

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=xmqq7fbo7ecl.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=ville.skytta@iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.