Re: Where to send tag patches?

--rwEMma7ioTxnRzrJ
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline

On Fri, May 21, 2004 at 05:29:03PM +0200, Erich Schubert wrote:

> How much feedback should the user get? Should we handle errors, or
> should the submitter recieve them? Should he get a list of packages that
> he modified? Or just a "thanks for your contribution"?
> The destination address is [email protected]

I'd suggest a report on how the input went, like:

  The tag patch you sent on xxx, received on xxx has been processed
  successfully.

  Thanks for your contribution.

  The Central Debtags Archive

Or:

  The tag patch you sent on xxx, received on xxx has not been processed
  because of xxx.  You should try xxx./You should report xxx.

  Thanks for your contribution.

  The Central Debtags Archive

A feedback mail would serve both as a confirmation that the work has
been considered and as a deterrent for multiple sends (you play too much
with the send button, you receive a lot of mail :) .


On Fri, May 21, 2004 at 05:56:06PM +0200, Erich Schubert wrote:

> > The destination address is [email protected]
> You can now submit debtag diff files to this address by attaching them
> to a email as mime (or hopefully uuencoded, too) and adding
> "-- DEBTAGS DIFF V0.1 --" to the first line.
> I just added a tag to a package this way. ;-)

I've sent the first test mails with the categorization I did so far.
How did it go?

If everything is ok, and if the messages are parsed automatically
witout your intervention, I'll go on and upload the send-enabled
debtags-edit.

If there have been errors or you need to parse messages by hand please
tell me, as this interface tends to make it simple to push the
submit button and I could try changing it a bit.  (however, I think it's
not a bad idea to have submissions to be a simple thing, and the program
is quite neat that way!)


Ciao,

Enrico

--
GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <[email protected]>

--rwEMma7ioTxnRzrJ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFArp5C9LSwzHl+v6sRAq6GAJ0fOrLd4MtkD7ckQKBxzBe15tF0tQCggDRa
w5LsPl7ltfq7NkHGQs0226c=
=2wFL
-----END PGP SIGNATURE-----

--rwEMma7ioTxnRzrJ--