git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Nov 2019, #02; Fri, 8)
Date: Fri, 8 Nov 2019 08:44:15 -0800	[thread overview]
Message-ID: <CABPp-BHLAdTDaooQu2YXGcTEtqQrOwZ7cuQNhNuFEnV-yA0FiA@mail.gmail.com> (raw)
In-Reply-To: <xmqqeeyin4kx.fsf@gitster-ct.c.googlers.com>

On Fri, Nov 8, 2019 at 12:43 AM Junio C Hamano <gitster@pobox.com> wrote:
> * en/doc-typofix (2019-11-07) 11 commits
>  - Fix spelling errors in no-longer-updated-from-upstream modules
>  - multimail: fix a few simple spelling errors
>  - sha1dc: fix trivial comment spelling error
>  - Fix spelling errors in test commands
>  - Fix spelling errors in messages shown to users
>  - Fix spelling errors in names of tests
>  - Fix spelling errors in comments of testcases
>  - Fix spelling errors in code comments
>  - Prefer 'up-to-date' spelling
>  - Fix spelling errors in documentation outside of Documentation/
>  - Documentation: fix a bunch of typos, both old and new
>
>  Docfix.
>
>  Will merge to 'next'.

Wait!  I thought we wanted to eject the uptodate vs. up-to-date patch.
Do you want to do that, or do you want me to send a re-roll where the
only change is removing that patch?  (The other patches are fine to
merge to next if you want.)

See https://public-inbox.org/git/CABPp-BECJezMeg1pZyQijkBDooA_834weeg_2hsZ1Vonm-tAEQ@mail.gmail.com/

  parent reply	other threads:[~2019-11-08 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  8:40 What's cooking in git.git (Nov 2019, #02; Fri, 8) Junio C Hamano
2019-11-08 15:00 ` Matheus Tavares Bernardino
2019-11-14  6:35   ` Matheus Tavares Bernardino
2019-11-08 16:44 ` Elijah Newren [this message]
2019-11-10  6:59   ` 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

  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=CABPp-BHLAdTDaooQu2YXGcTEtqQrOwZ7cuQNhNuFEnV-yA0FiA@mail.gmail.com \
    --to=newren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).