all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Submitting patches: need I do more than send them to the bug tracker?
@ 2018-10-24 14:10 Daniel Pittman
  2018-10-27 22:24 ` Noam Postavsky
  0 siblings, 1 reply; 4+ messages in thread
From: Daniel Pittman @ 2018-10-24 14:10 UTC (permalink / raw)
  To: emacs-devel

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

G'day.  I'm sorry to trouble y'all, but I'm trying to work out if I have
missed something when I read through the contributing guide.

I have a couple of patches in the bug tracker at the moment, one feature,
and one bug fix, which have attracted no response.  In the former case it
has been five days, which I had assumed would be enough time to get some
sort of response.

Now, I'm not asking for special treatment, or someone to rush and review
the code, but rather, to ensure that I have done all the right things to
get this into the queue for Emacs.  I'd rather ask than miss something.

The two tickets in question are:

Feature added to emacsclient, five days old:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33095

Bug fix for `vc-hg-find-file-hook', one day old:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33129

Again, if getting them there is all that was needed, great, and I'm happy
for them to be reviewed at whatever schedule suits you best.

[-- Attachment #2: Type: text/html, Size: 1370 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Submitting patches: need I do more than send them to the bug tracker?
  2018-10-24 14:10 Submitting patches: need I do more than send them to the bug tracker? Daniel Pittman
@ 2018-10-27 22:24 ` Noam Postavsky
  2018-10-28 15:43   ` Eli Zaretskii
  0 siblings, 1 reply; 4+ messages in thread
From: Noam Postavsky @ 2018-10-27 22:24 UTC (permalink / raw)
  To: slippycheeze; +Cc: Emacs developers

On Wed, 24 Oct 2018 at 10:15, Daniel Pittman <slippycheeze@google.com> wrote:

> I have a couple of patches in the bug tracker at the moment, one feature, and one bug fix, which have attracted no response.  In the former case it has been five days, which I had assumed would be enough time to get some sort of response.
>
> Now, I'm not asking for special treatment, or someone to rush and review the code, but rather, to ensure that I have done all the right things to get this into the queue for Emacs.  I'd rather ask than miss something.

If you don't get a response to a patch, sending a short message to
make sure it hasn't gotten lost like you've done is the right thing to
do. I would generally say to wait a full week.

> The two tickets in question are:
>
> Feature added to emacsclient, five days old:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33095
>
> Bug fix for `vc-hg-find-file-hook', one day old:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33129
>
> Again, if getting them there is all that was needed, great, and I'm happy for them to be reviewed at whatever schedule suits you best.

I see Eli has by now applied the first one; the second looks
reasonable, though not being an hg user, I'd hesitate to apply it
myself.



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Submitting patches: need I do more than send them to the bug tracker?
  2018-10-27 22:24 ` Noam Postavsky
@ 2018-10-28 15:43   ` Eli Zaretskii
  2018-10-28 17:01     ` Daniel Pittman
  0 siblings, 1 reply; 4+ messages in thread
From: Eli Zaretskii @ 2018-10-28 15:43 UTC (permalink / raw)
  To: Noam Postavsky; +Cc: slippycheeze, emacs-devel

> From: Noam Postavsky <npostavs@gmail.com>
> Date: Sat, 27 Oct 2018 18:24:18 -0400
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> If you don't get a response to a patch, sending a short message to
> make sure it hasn't gotten lost like you've done is the right thing to
> do. I would generally say to wait a full week.

Yes, a good advice.  I usually wait for comments for at least a week,
if I have no comments myself.



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Submitting patches: need I do more than send them to the bug tracker?
  2018-10-28 15:43   ` Eli Zaretskii
@ 2018-10-28 17:01     ` Daniel Pittman
  0 siblings, 0 replies; 4+ messages in thread
From: Daniel Pittman @ 2018-10-28 17:01 UTC (permalink / raw)
  To: eliz; +Cc: npostavs, emacs-devel

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Sun, Oct 28, 2018 at 11:43 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Noam Postavsky <npostavs@gmail.com>
> > Date: Sat, 27 Oct 2018 18:24:18 -0400
> > Cc: Emacs developers <emacs-devel@gnu.org>
> >
> > If you don't get a response to a patch, sending a short message to
> > make sure it hasn't gotten lost like you've done is the right thing to
> > do. I would generally say to wait a full week.
>
> Yes, a good advice.  I usually wait for comments for at least a week,
> if I have no comments myself.
>

Great, thank you.  That was roughly what I figured was reasonable, but ...
I'm occasionally too good at missing things. :)

Thank you for applying (and reviewing) my changes, also.

[-- Attachment #2: Type: text/html, Size: 1170 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-10-28 17:01 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-10-24 14:10 Submitting patches: need I do more than send them to the bug tracker? Daniel Pittman
2018-10-27 22:24 ` Noam Postavsky
2018-10-28 15:43   ` Eli Zaretskii
2018-10-28 17:01     ` Daniel Pittman

Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.