Re: LOG after commit, What it is?

[danilo gnome org (Danilo Åegan)]

Hi Gurban,

Note that you should actually *read* the guides aimed at translators:
     http://developer.gnome.org/projects/gtp/resources.html
and in particular:
     http://developer.gnome.org/doc/tutorials/gnome-i18n/translator.html

which says at the end of numbered-steps:
  15. Commit everything (don't forget to add ChangeLog-style commit comment):
      cvs commit

(note what kind of comment you should add).

Today at 9:24, Gurban M. Tewekgeli wrote:

>   When I commit a po file, vi appeared for a log file.

Fix your EDITOR environment variable (eg. point it to "emacsclient
-n", run emacs and do M-x server-start), and you won't have vi popping
up for you ;-)

J/k, don't mind me if you prefer vi for editting.

> What I must write for the log file. Have it a format
> like Changelog or no?

You may use ChangeLog format (some developers/translators prefer
this), or you may use simple messages.  For translations, which
usually touch one or two files with changes of the same nature, I
prefer using simple messages like:

  "Updated Serbian translation."

They look better when one does "cvs log", or browses CVS through
something like ViewCVS.  There's no need to mention dates or files,
since that's what CVS tracks itself.  If there're several unrelated
changes in one commit, then you'd better use ChangeLog format.

Once you get proficient enough that you don't need to read what files
have been changed (perhaps you changed some files without wanting to
-- that's good about having this appear in an editor, you check prior
to commit), you may also go the quicker route:

  cvs ci -m 'Updated Serbian translation.'

Of course, replace all occurences of "Serbian", and use "-z3" if you
don't have it in your ~/.cvsrc.

Cheers,
Danilo