public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Mitchell Hentges <mhentges@mozilla.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin-patches@cygwin.com
Subject: Re: [PATCH 1/1] Cygwin: console: Maintain EXTENDED_FLAGS state
Date: Fri, 11 Feb 2022 00:10:13 -0500	[thread overview]
Message-ID: <CAAvot8_9gycBDpQ2VfiGrKLakx7RL88tjf1OYfmMODMYo4g=sw@mail.gmail.com> (raw)
In-Reply-To: <20220211091204.409213793d1c2e4b961299eb@nifty.ne.jp>

For future reference, as my git commit message lost some information: the
"[1]" link I was trying to refer to was to here:
https://www.os2museum.com/wp/disabling-quick-edit-mode/
This was my first experience working with email-based patch contributing,
so I apologize for the mis-steps here.
Thanks again :)

On Thu, Feb 10, 2022 at 7:12 PM Takashi Yano <takashi.yano@nifty.ne.jp>
wrote:

> On Thu, 10 Feb 2022 10:40:36 -0500
> Mitchell Hentges wrote:
> > Thanks, I appreciate it.
> > The initial send was via GMail, but I've wired up git-send-email to
> msmtp,
> > and I'm hoping that it's happy now - at least, it looks like tabs are
> being
> > preserved now, which is a good sign.
>
> Pushed along with modifying the commit message.
>
> Thansk!
>
> --
> Takashi Yano <takashi.yano@nifty.ne.jp>
>


-- 
Mitchell Hentges
Engineering Workflow
Mozilla

      reply	other threads:[~2022-02-11  5:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  0:09 Mitchell Hentges
2022-02-10  8:07 ` Takashi Yano
2022-02-10 15:38   ` Mitchell Hentges
2022-02-10 15:40     ` Mitchell Hentges
2022-02-11  0:12       ` Takashi Yano
2022-02-11  5:10         ` Mitchell Hentges [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='CAAvot8_9gycBDpQ2VfiGrKLakx7RL88tjf1OYfmMODMYo4g=sw@mail.gmail.com' \
    --to=mhentges@mozilla.com \
    --cc=cygwin-patches@cygwin.com \
    --cc=takashi.yano@nifty.ne.jp \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).