public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: Tea Inside Mailing List <[email protected]>
Subject: Re: First Message
Date: Sat, 22 Jan 2022 11:19:18 +0700	[thread overview]
Message-ID: <CAFBCWQL4MK-MajbRQC=kWq+8XNRr0XQ60jHVg0QrByUEvK=5ng@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qOtreBSqgXotKT7dh65KzF_hJhd_6tKbOWMJ_QfD+xZAw@mail.gmail.com>

On Sat, Jan 22, 2022 at 11:18 AM Alviro Iskandar Setiawan wrote:
>
> On Sat, Jan 22, 2022 at 11:14 AM Ammar Faizi <[email protected]> wrote:
> >
> > On Sat, Jan 22, 2022 at 11:07 AM Alviro Iskandar Setiawan wrote:
> > >
> > > On Sat, Jan 22, 2022 at 11:05 AM Alviro Iskandar Setiawan
> > > <[email protected]> wrote:
> > > >
> > > > On Sat, Jan 22, 2022 at 11:01 AM Ammar Faizi <[email protected]> wrote:
> > > > >
> > > > > On Sat, 22 Jan 2022 10:56:43 +0700 Ammar Faizi wrote:
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > This is the first message I send to the Tea Inside Mailing List. Reply
> > > > > > with something if you receive it.
> > > > >
> > > > > Added Viro to the CC list.
> > > >
> > > > nice sir, i got the email
> > >
> > > we will use [email protected] for code review inbox sir?
> >
> > Yes, let's use it. Send me pull requests and patches with
> >
> > Cc: Tea Inside Mailing List <[email protected]>
> >
>
> oc oc, i will try to send a simple patch to start using this :v

Go ahead :)

-- 
Ammar Faizi

      reply	other threads:[~2022-01-22  4:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22  3:56 First Message Ammar Faizi
2022-01-22  4:00 ` Ammar Faizi
2022-01-22  4:05   ` Alviro Iskandar Setiawan
2022-01-22  4:07     ` Alviro Iskandar Setiawan
2022-01-22  4:14       ` Ammar Faizi
2022-01-22  4:18         ` Alviro Iskandar Setiawan
2022-01-22  4:19           ` Ammar Faizi [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='CAFBCWQL4MK-MajbRQC=kWq+8XNRr0XQ60jHVg0QrByUEvK=5ng@mail.gmail.com' \
    [email protected] \
    [email protected] \
    [email protected] \
    /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