[PATCH 01/12] git-grep: read config

Signed-off-by: Nguyễn Thái Ngọc Duy <redacted>
---
 builtin-grep.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/builtin-grep.c b/builtin-grep.c
index 631129d..cc9ba6b 100644
--- a/builtin-grep.c
+++ b/builtin-grep.c

@@ -517,6 +517,8 @@ int cmd_grep(int argc, const char **argv, const char *prefix)
 	const char **paths = NULL;
 	int i;
 
+	git_config(git_default_config, NULL);
+
 	memset(&opt, 0, sizeof(opt));
 	opt.prefix_length = (prefix && *prefix) ? strlen(prefix) : 0;
 	opt.relative = 1;

-- 
1.5.5.GIT

On Wed, Jul 23, 2008 at 09:55:35PM +0700, Nguyễn Thái Ngọc Duy wrote:

Signed-off-by: Nguyễn Thái Ngọc Duy <redacted>

The commit message is a bit lacking...what config are we interested in?

-Peff

On 7/25/08, Jeff King [off-list ref] wrote:

On Wed, Jul 23, 2008 at 09:55:35PM +0700, Nguyen Thai Ngoc Duy wrote:

 >
 > Signed-off-by: Nguyễn Thái Ngọc Duy [off-list ref]


The commit message is a bit lacking...what config are we interested in?

core.sparsecheckout, but I will probably stay away from config.

-- 
Duy

On Thu, Jul 24, 2008 at 8:45 PM, Nguyen Thai Ngoc Duy [off-list ref] wrote:

Something went wrong replying here possibly? Or is it just me who is
receiving empty messages? (At least the 3rd empty mail I see.)

-- 
Cheers,

Sverre Rabbelier

On Fri, Jul 25, 2008 at 01:45:58AM +0700, Nguyen Thai Ngoc Duy wrote:

quoted

The commit message is a bit lacking...what config are we interested in?

core.sparsecheckout, but I will probably stay away from config.

Right, I kind of guessed that from reading the rest of the series. But
that sort of "why" really should go into the commit message.

-Peff

On 7/25/08, Sverre Rabbelier [off-list ref] wrote:

On Thu, Jul 24, 2008 at 8:45 PM, Nguyen Thai Ngoc Duy [off-list ref] wrote:
 >

 Something went wrong replying here possibly? Or is it just me who is
 receiving empty messages? (At least the 3rd empty mail I see.)

I blame gmail MTA or my name's having non-ascii chars in it. Combining
those two, it produces base64-encoded messages, which are usually
refused by vger.
-- 
Duy

On 7/25/08, Jeff King [off-list ref] wrote:

On Fri, Jul 25, 2008 at 01:45:58AM +0700, Nguyen Thai Ngoc Duy wrote:

 > > The commit message is a bit lacking...what config are we interested in?
 >
 > core.sparsecheckout, but I will probably stay away from config.


Right, I kind of guessed that from reading the rest of the series. But
 that sort of "why" really should go into the commit message.

There was "why" in the commit before but I wanted to make the first
two patches independent to this series. Turns out bad, I think :)
-- 
Duy

On Thu, Jul 24, 2008 at 9:03 PM, Nguyen Thai Ngoc Duy [off-list ref] wrote:

On 7/25/08, Sverre Rabbelier [off-list ref] wrote:

quoted

On Thu, Jul 24, 2008 at 8:45 PM, Nguyen Thai Ngoc Duy [off-list ref] wrote:
 >

 Something went wrong replying here possibly? Or is it just me who is
 receiving empty messages? (At least the 3rd empty mail I see.)

I blame gmail MTA or my name's having non-ascii chars in it. Combining
those two, it produces base64-encoded messages, which are usually
refused by vger.

Curiously enough, in the first mail there -are- non-asci characters in
your name, in the 'empty' mail there are non, instead the 'letter
decorations' were removed.

-- 
Cheers,

Sverre Rabbelier

On Thu, Jul 24, 2008 at 2:53 PM, Sverre Rabbelier [off-list ref] wrote:

On Thu, Jul 24, 2008 at 8:45 PM, Nguyen Thai Ngoc Duy [off-list ref] wrote:

quoted

Something went wrong replying here possibly? Or is it just me who is
receiving empty messages? (At least the 3rd empty mail I see.)

Here's what's going on.

1. Gmail will often send messages as base64 encoded, inline. i.e.:

   Content-Type: text/plain; charset=UTF-8
   Content-Transfer-Encoding: base64
   Content-Disposition: inline

2. Majordomo is dumb dumb dumb and adds the standard list footer to
the message. It should probably either not add the footer to such
messages, or it should do it correctly by base64 decoding them, adding
the footer, then re-encoding. Anyway, what it sends out is:

   [... prior base64 encoded lines elided ...]
   b3V0LCBidXQgSSB3aWxsIHByb2JhYmx5IHN0YXkgYXdheSBmcm9tIGNvbmZpZy4KCi0tIApEdXkK
   --
   To unsubscribe from this list: send the line "unsubscribe git" in
   the body of a message to majordomo@vger.kernel.org
   More majordomo info at  http://vger.kernel.org/majordomo-info.html

3. Gmail is dumb dumb dumb and cannot decode such "corrupted"
messages. They display as completely blank. If you go to gmane you can
see the message is fine. (I think gmane strips the majordomo added
footer.)

I've filed a bug against gmail multiple times about this. No idea if
they'll ever fix it.

I also sent an email to git-owner@vger.kernel.org (which I think was
/dev/null'ed) offering to patch Majordomo, but got no reply.

I wonder if such a mailing list footer is useful in the first place.
Perhaps it could just be disabled.

Anyway, my offer to "fix" majordomo still stands. Perhaps someone
knows who I should contact at vger.kernel.org to find out whether
they're willing to accept a patch.

j.