git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Pay attention to GIT_DIR when searching the git directory
Date: Mon, 5 May 2008 17:30:29 +0200	[thread overview]
Message-ID: <20080505153029.GA12733@alea.gnuu.de> (raw)
In-Reply-To: <m3r6cg6dur.fsf@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

Hi Jakub,

Jakub Narebski schrieb am Mon 05. May, 07:10 (-0700):
> 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.

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.

> > 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)

[-- Attachment #2: Digital signature http://en.wikipedia.org/wiki/OpenPGP --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-05-05 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  0:09 [PATCH] Pay attention to GIT_DIR when searching the git directory Jörg Sommer
2008-05-05 11:36 ` Johannes Schindelin
2008-05-05 12:53   ` Jörg Sommer
2008-05-05 13:39     ` Johannes Schindelin
2008-05-05 14:10     ` Jakub Narebski
2008-05-05 15:30       ` Jörg Sommer [this message]
2008-05-05 16:33         ` Johannes Schindelin
2008-05-05 16:48         ` Jakub Narebski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080505153029.GA12733@alea.gnuu.de \
    --to=joerg@alea.gnuu.de \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).