Mailinglist Archive: opensuse-buildservice (269 mails)

< Previous Next >
[opensuse-buildservice] How much user guidance in hermes notifications?
  • From: Susanne Oberhauser <froh@xxxxxxxxxx>
  • Date: Mon, 15 Sep 2008 12:30:40 +0200
  • Message-id: <s2ivdwxvgz3.fsf@xxxxxxxxxxxxx>

I'd like to extend the hermes messages with some little guidance on
what to do with each of them.

For example, a change request currently just gives the dry facts of
what has been submitted where to.

I'm proposing the message to also contain the osc command line to show
the diff, and the osc command lines to accept, decline (or retract),
for cut&paste, like this:

@subject: submit-request #1543 created (target: openSUSE:Factory)

User <maw> has submitted the request to accept

project: GNOME:Factory
package: poppler
revision: a110b4214d63ac92f41eea8d7a457d85


project: openSUSE:Factory
package: poppler

Please handle the request...
To review:
osc submitreq show --diff 1543

To accept:
osc submitreq accept 1543

To decline:
osc submitreq decline 1543 --message "please resubmit with fixed

To retract:
os submitreq delete 1543 --message "actually this change won't work,

For details, please see

This is how it currently looks like:

@subject: submit-request #1543 created (target: openSUSE:Factory)

submit-request #1543 created by maw

project: GNOME:Factory
package: poppler
revision: a110b4214d63ac92f41eea8d7a457d85

project: openSUSE:Factory
package: poppler

Alternatatively we could just point to the collaboration docu, and
leave the typing ot the inclined user.

I'd do similar changes to the other messages, where it makes sense.


Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business
OPS Engineering Maxfeldstraße 5
Processes and Infrastructure Nürnberg
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >