Thread (8 messages) flat view 8 messages, 3 authors, 2016-06-15

Re: [PATCH] Pay attention to GIT_DIR when searching the git directory

From: Jörg Sommer <hidden>
Date: 2016-06-15 22:44:34

Hi Jakub,

Jakub Narebski schrieb am Mon 05. May, 07:10 (-0700):
Jörg Sommer [off-list ref] writes:
quoted
Johannes Schindelin schrieb am Mon 05. May, 12:36 (+0100):
quoted
quoted
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.
Well, if this is the prefered form, I'll use it. But I don't like it,
because the affected file is a piece of information that's already in the
commit object. And it makes the :/ syntax useless, because in a series of
commits all commits start with the same string: the filename. Thirdly, in
gitk I've the problem that the space is very limited (because of my
screen) and it is very annoying to see the same string at the begin of
every commit message, especially when I've filtered for one file.
quoted
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.
Are there any plans to write them down?

Should I resend the patch or can Junio fix the commit message? I would
take your suggestion.

Bye, Jörg.
-- 
Geld allein macht nicht glücklich, aber es ist besser in einem Taxi zu
weinen, als in der Straßenbahn.
	       	   	       			(Marcel Reich‐Ranicki)

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help