Magnus Hagander wrote:
> On Wed, Mar 30, 2016 at 7:47 PM, Alvaro Herrera
> wrote:
>
> > José Luis Tallón wrote:
> >
> > > Just wanted to suggest two minor mods to the review e-mails
> > > auto-generated by the app:
> > >
> > > * Prepend a [review] tag to the e-mail
On Wed, Apr 6, 2016 at 2:11 PM, Magnus Hagander wrote:
> On Wed, Mar 30, 2016 at 7:47 PM, Alvaro Herrera
> wrote:
>
>> José Luis Tallón wrote:
>>
> > * Auto-CC the patch author on this e-mail
>> > I guess this should speed up reactions / make
On Wed, Mar 30, 2016 at 7:47 PM, Alvaro Herrera
wrote:
> José Luis Tallón wrote:
>
> > Just wanted to suggest two minor mods to the review e-mails
> > auto-generated by the app:
> >
> > * Prepend a [review] tag to the e-mail subject
> > ... so that e-mails sent
On Wed, Mar 30, 2016 at 1:47 PM, Alvaro Herrera
wrote:
> José Luis Tallón wrote:
>> Just wanted to suggest two minor mods to the review e-mails
>> auto-generated by the app:
>>
>> * Prepend a [review] tag to the e-mail subject
>> ... so that e-mails sent to
* José Luis Tallón (jltal...@adv-solutions.net) wrote:
> * Prepend a [review] tag to the e-mail subject
> ... so that e-mails sent to -hackers will read " [HACKERS]
> [review] "
Eh, I'm not against it but not sure it's all that necessary either.
> * Auto-CC the patch author on this e-mail
>
José Luis Tallón wrote:
> Just wanted to suggest two minor mods to the review e-mails
> auto-generated by the app:
>
> * Prepend a [review] tag to the e-mail subject
> ... so that e-mails sent to -hackers will read " [HACKERS] [review]
> "
Changing the subject of an email causes Gmail
Hello,
Just wanted to suggest two minor mods to the review e-mails
auto-generated by the app:
* Prepend a [review] tag to the e-mail subject
... so that e-mails sent to -hackers will read " [HACKERS]
[review] "
* Auto-CC the patch author on this e-mail
I guess this should
Hi!
I'm about to start some upgrades on the machine running
commitfest.postgresql.org. The app itself won't change, but the underlying
OS and webserver will, so there will be some disruptions of service and
some strange and scary error messages for a while.
Hopefully it will take less than an
On Wed, Jan 6, 2016 at 4:50 PM, Magnus Hagander wrote:
> Hi!
>
> I'm about to start some upgrades on the machine running
> commitfest.postgresql.org. The app itself won't change, but the
> underlying OS and webserver will, so there will be some disruptions of
> service and
On Thu, May 7, 2015 at 9:17 PM, Fabien COELHO coe...@cri.ensmp.fr wrote:
Hello,
Some comments/bug report about the commitfest web app which just bite me:-)
When creating a patch with the commitfest app, if the thread does not
exist the application seems to reject the creation, so you may
ISTM that an additional Duplicate or To remove status could be a tag for
admins to remove the entries?
This looks like an overkill to me. Entries with the same description
headline mean the same thing.
Sure.
My point was to provide a mean to signal explicitely that an entry can be
Hello,
Some comments/bug report about the commitfest web app which just bite
me:-)
When creating a patch with the commitfest app, if the thread does not
exist the application seems to reject the creation, so you may resubmit
because you know the thread is going to exist soon... Well, this
Hello Michael,
It is possible to remove patches from the set, but administrator rights
are necessary.
Good. Maybe this right could be granted to the person who as created the
patch entry in the CF?
If there are duplicated entries that you would like to get removed,
simply mention them
On Fri, May 8, 2015 at 4:17 AM, Fabien COELHO wrote:
Then there is no way to remove a patch from the application. You end up
marking them as Rejected, which does not make much sense, see the bottom
of the 2015-06 commitfest list...
Maybe a Duplicate status would be better, and the ability to
On Fri, May 8, 2015 at 10:35 AM, Fabien COELHO coe...@cri.ensmp.fr wrote:
Hello Michael,
It is possible to remove patches from the set, but administrator rights
are necessary.
Good. Maybe this right could be granted to the person who as created the
patch entry in the CF?
Er, well...
On Fri, May 8, 2015 at 11:54 AM, Fabien COELHO coe...@cri.ensmp.fr wrote:
I'm fine to do this cleanup btw.
ISTM that an additional Duplicate or To remove status could be a tag for
admins to remove the entries?
This looks like an overkill to me. Entries with the same description
headline
I'm fine to do this cleanup btw.
ISTM that an additional Duplicate or To remove status could be a tag
for admins to remove the entries?
Feel free to remove the stupid Rejected entries at the end of the 2015-06
CF: there are currently 11 pgbench allow '=' in \set (mine) and 2
configure
I use rss to follow up on patches that I'm interested in and it's the
second time I was wonering where my patch has gone in the commitfest app
due to $Topic.
Is this a known limitation?
If yes: Is there a way to change this?
If yes: Can/shall I help?
If yes: Where should I start?
Regards,
Brar Piening wrote:
I use rss to follow up on patches that I'm interested in and it's the
second time I was wonering where my patch has gone in the commitfest
app due to $Topic.
Just after pushing the send button my RSS-feed got updated and contained
the relevant information.
Sorry for the
I haven't paid much attention to the new commitfest app until now.
Generally, it looks good, but I'm wondering if we should have a
committer field.
I'm thinking of picking up at least the following items if/when they are
ready, but such a thing might help us to make sure we don't trip over
20 matches
Mail list logo