From: Jakub Narebski <jnareb@gmail.com>
Date: Mon, 05 May 2008 14:10:53 GMT
Subject: Re: [PATCH] Pay attention to GIT_DIR when searching the git directory
Message-ID: <m3r6cg6dur.fsf@localhost.localdomain>
In-Reply-To: <20080505125302.GA11523@alea.gnuu.de>

Jörg Sommer <joerg@alea.gnuu.de> writes:

> Johannes Schindelin schrieb am Mon 05. May, 12:36 (+0100):

> > If you do not say _what_ is affected by the change, you only confuse
> > the readers.
> 
> Do you want something like “initialization: Pay attention to GIT_DIR when
> searching the git directory”?

I think the idea was to use
  "contrib/hooks/setgitperms: Use GIT_DIR if set"
or something like that.
 
> Is there a document with guidelines for commit messages, e.g. write the
> first letter upper or lower case?

There are a few unwritten conventions.  You can always check existing
commit messages, via

  $ git log --pretty=oneline --abbrev-commit --no-merges

and see that commit title (first line of commit message) is either
short sentence starting with upper case, bt without fullstop, or
sentence preceded by the subsystem affected, using "<subsystem>:"
prefix.

Examples:
  Fix use after free() in builtin-fetch
  git-svn: detect and fail gracefully when dcommitting to a void

-- 
Jakub Narebski
Poland
ShadeHawk on #git