From: Thiago Jung Bauermann <bauermann@kolabnow.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] Add EditorConfig file
Date: Sat, 11 Jun 2022 00:23:12 -0300 [thread overview]
Message-ID: <877d5n51dl.fsf@kolabnow.com> (raw)
In-Reply-To: <20220611003730.M124658@dcvr>
Eric Wong <e@80x24.org> writes:
> Thanks, pushed.
Thank you!
> Also added the entry to MANIFEST (git ls-files >MANIFEST)
> to keep build/dist system happy.
Ah, I wasn't aware of that. Thank you for taking care of it.
--
Thanks
Thiago
prev parent reply other threads:[~2022-06-11 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:51 [PATCH] Add EditorConfig file Thiago Jung Bauermann
2022-06-11 0:37 ` Eric Wong
2022-06-11 3:23 ` Thiago Jung Bauermann [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d5n51dl.fsf@kolabnow.com \
--to=bauermann@kolabnow.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.org \
/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).