From: Federico Tedin <federicotedin@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, emacs-devel@gnu.org
Subject: Re: Submitted patches
Date: Fri, 22 Mar 2019 18:12:30 -0300 [thread overview]
Message-ID: <87imwa4nr5.fsf@gmail.com> (raw)
In-Reply-To: <83zhpns6qh.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Mar 2019 10:33:58 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> Date: Fri, 22 Mar 2019 00:31:04 +0000
>> Cc: emacs-devel@gnu.org
>>
>> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34147
>> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34065
>>
>> Thanks for working on these; both LGTM FWIW, but I'm relatively new
>> around here. ;)
>
> Thanks for reviewing the patches.
>
>> Speaking from personal experience rather than authority, it is not
>> unusual to wait a bit longer than a week for a reply.
>
> Yeah, something like 2 weeks is a better rule of thumb.
>
> In general, the lack of any response in the first week is a good sign,
> especially for short submissions: it mostly means nothing really
> incorrect was very obvious at the first reading.
Thanks, Basil and Eli, for the feedback. Next time I'll make sure at
least to weeks.
> Your patches are on my queue. Sorry, I've been a bit more busy
> lately.
>
> It's okay to send a reminder, but please send them to the same address
> where you sent the patches. Posting here is a kind of emergency
> measure, so I'd say only do that if several pings to the bug tracker
> get no response at all.
>
> Thanks.
No problem, I'll send future pings through the bug tracker, then.
Thanks again!
next prev parent reply other threads:[~2019-03-22 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 23:17 Submitted patches Federico Tedin
2019-03-22 0:31 ` Basil L. Contovounesios
2019-03-22 7:33 ` Eli Zaretskii
2019-03-22 21:12 ` Federico Tedin [this message]
2019-03-22 7:28 ` Eli Zaretskii
2019-03-22 7:56 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imwa4nr5.fsf@gmail.com \
--to=federicotedin@gmail.com \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).