[PATCH 0/2] gitignore and string.h updates for GPGME

Werner Koch wk at gnupg.org
Fri Apr 13 14:58:12 CEST 2012

On Fri, 13 Apr 2012 12:59, marcus.brinkmann at ruhr-uni-bochum.de said:
>>     * doc/.gitignore, lang/cl/.gitignore, src/.gitignore
>>     * tests/.gitignore, tests/gpg/.gitignore, tests/gpgsm/.gitignore
>>     * tests/opassuan/.gitignore: Add subdir-specific ignore rules, so `git
>>     status` can focus on interesting changes.
> Are you sure?  This looks wrong to me, as a "*" starts a new item, and

Yes.  The asterisk indicates a list of files.  The missing colon at the
end of the line indcates that more lines for this item will follow.  You
don't use an asterisk if it is another function:

      * foo.c (usage_1, usage_2, usage)
      (help): Add help strings.

> doesn't seem right to me, and I never did that.  It's also not how emacs
> fill-paragraph formats it when confronted with the situation...

That has never worked correctly ;) The standards file doesn't tell it
explicitly, probably because the case of only new files with no function
names is rare.  However it states:

     Separate unrelated change log entries with blank lines.  When two
  entries represent parts of the same change, so that they work together,
  then don't put blank lines between them.  Then you can omit the file
  name and the asterisk when successive entries are in the same file.

At least this is my interpretation.

BTW, did anyone worked on Magit's 'C' command so work more similar to
C-x a 4 ?

> Thanks,
> Marcus
> _______________________________________________
> Gnupg-devel mailing list
> Gnupg-devel at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gnupg-devel mailing list