Re: CVS line for Source Code Header
Christian Schoepplein <christian.schoepplein <at> otrs.com>
2007-07-12 16:21:30 GMT
HI Dan,
On Do, Jul 12, 2007 at 11:43:32 -0400, Dan King wrote:
> I am creating the NotificationMotd.pm file listed in the Dev Manual
Cool :).
> and I
> was curious if someone could explain the CVS line for the Source code
> header and what each part means and how I would write that line. The
> example from the NotificationMotd.pm file is:
>
>
>
> # $Id: module-format.xml,v 1.17.4.1 2007/03/20 11:13:40 martin Exp $
>
>
>
> I understand that I should replace the date in the line with todays date
> and time that I created the format. But the part I am confused about is
> what module-format.xml is or means, if the version number is the version
> of the file I am writing or the version of OTRS I am using. Also, what
> does the "martin Exp $" part mean?
The cvs line in the file does not need to be edited, the cvs server does
this for us :). So dont care about the line :). However, the format is:
# $Id:
-> This is a marker for the cvs server that tells that the line is
starting
module-format.xml,
-> Just the name of the file.
v 1.17.4.1
-> The current version number of the file
2007/03/20 11:13:40
-> The date and time when the file was commited the last time.
martin
-> The user who committed the file the last time
Exp $
-> End of the line where all this information are stored.
> Dan King
Regards,
Christian
--
--
((otrs)) :: OTRS GmbH :: Norsk-Data-Strasse 1 :: 61352 Bad Homburg
Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18
http://www.otrs.com/ :: Communication with success!
Geschäftsführer: André Mindermann, Martin Edenhofer
Handelsregister: HRB 9452 Bad Homburg
Steuernummer: 003/240/97521
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
) "hey joe, could you please..." * SOAP and who created the ticket (article_sender_type) * the user * one of his IT-key-users * one member of the IT-stuff (OTRS-agent) * some kind of system monitoring (like nagios or client-HW-monitoring-tool) I think todays OTRS lacks in the possibility of doing the ticket-creation in such a specific way, that the above mentioned scenaria can be distingushed (for analytic reasons). OK, if you create a ticket from a system-monitoring-tool via SOAP, you can add article_type = SOAP and article_sender_type = Monitoring to the database and can create the ticket in such a specific way, but you cannot manually create a ticket where * the IT-key-user of a department * told you during breakfast * that user x has some trouble with... The Web-GUI cannot handle that.
RSS Feed