From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Jörg Sommer" <joerg@alea.gnuu.de>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Pay attention to GIT_DIR when searching the git directory
Date: Mon, 5 May 2008 17:33:27 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0805051731350.30431@racer> (raw)
In-Reply-To: <20080505153029.GA12733@alea.gnuu.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1205 bytes --]
Hi,
On Mon, 5 May 2008, Jörg Sommer wrote:
> 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.
Well, I don't like that you thereby waste the time of those who look at
the commit message. By your reasoning, one might think that commit
messages are superfluous, because you can always read the patch, or go
back to the mailing list thread.
Ciao,
Dscho
> > There are a few unwritten conventions.
>
> Are there any plans to write them down?
Actually, they are written down implicitly. You can look at them with the
command "git log".
Ciao,
Dscho
next prev parent reply other threads:[~2008-05-05 16:34 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
2008-05-05 16:33 ` Johannes Schindelin [this message]
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=alpine.DEB.1.00.0805051731350.30431@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=joerg@alea.gnuu.de \
/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