git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/1] Fix incorrectly reported CPU in 32-bit Windows
Date: Thu, 07 Feb 2019 13:13:51 -0800	[thread overview]
Message-ID: <xmqq36oznvxs.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <pull.121.git.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Thu, 07 Feb 2019 02:46:05 -0800 (PST)")

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:

> This is yet another patch I forgot to upstream, and I hope that it will make
> it into v2.21.0-rc1.

I guess this affects nobody other than you and perhaps J6t, the
point not being "there are only just two" but being "all of them
know how to deal with possible breakages if any in this change".

I am tempted to bypass the usual "from pu down to next down to
master" dance on this one, because of that.

;-)


  parent reply	other threads:[~2019-02-07 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 10:46 [PATCH 0/1] Fix incorrectly reported CPU in 32-bit Windows Johannes Schindelin via GitGitGadget
2019-02-07 10:46 ` [PATCH 1/1] mingw: fix CPU reporting in `git version --build-options` Johannes Schindelin via GitGitGadget
2019-02-08 22:39   ` Eric Sunshine
2019-02-13  9:59     ` Johannes Schindelin
2019-02-07 21:13 ` Junio C Hamano [this message]
2019-02-07 22:41   ` [PATCH 0/1] Fix incorrectly reported CPU in 32-bit Windows Johannes Schindelin

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=xmqq36oznvxs.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@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).