From: Kyle Meyer <firstname.lastname@example.org>
To: Fatih Aydin <email@example.com>
Subject: Re: [PATCH] Margin added for overflow visibility problem
Date: Wed, 16 Dec 2020 05:48:57 GMT [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Fatih Aydin writes:
> Thanks for the suggestion, it's okay for me. I just wanted to make sure
> that the issue is clear for everyone by describing the steps.
> I also agree with waiting for CSS gurus.
Applied (5ee39c352). Thanks again.
next prev parent reply other threads:[~2020-12-16 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 8:57 [PATCH] Margin added for overflow visibility problem Fatih Aydin
2020-12-13 6:56 ` Kyle Meyer
2020-12-13 11:38 ` Fatih Aydin
2020-12-16 5:48 ` Kyle Meyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-06 8:27 Fatih Aydin
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).