From: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Make clear, when contributions will be ignored
Date: Tue, 05 Feb 2019 13:36:00 -0000 [thread overview]
Message-ID: <1bbf75ee385d87871f6777ec32d637d42e5b0dba.camel@aegee.org> (raw)
In-Reply-To: <0990b8acd4cc08f74c1bf314851a113711dbfa04.camel@aegee.org>
Hello,
the current way to come forward is to send biweekly manual reminders.
Will it help, if bugzilla is tweaked to send reminders every two weeks for ready-patches? This also has the advantage,
that people will not have to once update a patch in BZ and then send it over gcc-patches.
Regards
ÐилÑн
On Fri, 2018-12-07 at 10:55 +0000, ÐилÑн ÐалаÑзов wrote:
> Hello,
>
> will it help, if Bugzilla is reprogrammed to send automatically weekly
> reminders on all patches, that are not integrated yet?
>
> Will lt help, if I hire myself to integrate the patch, or shall I
> rather hire somebody to send reminders?
>
> If something can be done after sending a reminder, then it can be
> arranged also without reminders. In particular, dealing with reminders
> is avoidable extra work.
>
> Whether people are paid or not, does not change on the subject very
> much. I have experienced organizations, where people are not paid and
> they manage to tackle everything. I have seen organizations where
> people are paid and they do not get the management right.
>
> I am not speaking about having some strict time to get a response, but
> rather to ensure an answer in reasonable time. No answer in reasonable
> time is the same as ignorance â the subject of this thread.
>
> The patch I proposed on 27th Oct was first submitted towards GDB and
> then I was told to send it to GCC. Here I was told to sent it to GDB.
> What shall happen to quit the loop?
>
> In any case, if the common aim is to have a system where contributions
> do not get lost, then Iâm sure the workflows can be adjusted to achieve
> this aim.
>
> Regards
> ÐилÑн
>
>
> On Wed, 2018-12-05 at 17:37 +0000, Joseph Myers wrote:
> > On Wed, 5 Dec 2018, Segher Boessenkool wrote:
> >
> > > Patches are usually ignored because everyone thinks someone else will
> > > handle it.
> >
> > And in this case, it looks like this patch would best be reviewed first in
> > the GDB context - then once committed to binutils-gdb, the committer could
> > post to gcc-patches (CC:ing build system maintainers) requesting a commit
> > to GCC if they don't have write access to GCC themselves. I consider
> > synchronizing changes to such top-level files in either direction to be
> > obvious and not to need a separate review.
> >
next prev parent reply other threads:[~2019-02-05 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 7:36 Make claer, " Дилян Палаузов
2018-12-05 17:13 ` Segher Boessenkool
2018-12-05 17:37 ` Joseph Myers
2018-12-07 10:55 ` Make clear, " Дилян Палаузов
2018-12-21 8:08 ` +reminder+ " Дилян Палаузов
2019-02-05 13:36 ` Дилян Палаузов [this message]
2019-02-05 23:10 ` Joseph Myers
2019-02-06 12:46 ` Segher Boessenkool
2019-02-10 14:45 ` Дилян Палаузов
2019-02-10 20:59 ` Segher Boessenkool
2019-02-11 12:44 ` Дилян Палаузов
2019-02-11 14:01 ` Segher Boessenkool
2019-02-11 14:16 ` Дилян Палаузов
2019-02-11 16:27 ` Segher Boessenkool
2019-02-17 17:00 ` Дилян Палаузов
2019-02-17 19:13 ` Segher Boessenkool
2019-02-17 19:47 ` Дилян Палаузов
2018-12-05 17:17 ` Make claer, " Maciej W. Rozycki
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=1bbf75ee385d87871f6777ec32d637d42e5b0dba.camel@aegee.org \
--to=dilyan.palauzov@aegee.org \
--cc=gcc-patches@gcc.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.
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).