From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Teach repo-config the -l and --get-regexp options
Date: Sat, 11 Feb 2006 19:05:17 -0800 [thread overview]
Message-ID: <7vlkwhgtua.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.63.0602111306450.25997@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Happier?
Not really.
It still dumps core with:
[core]
boolvarsaretrueiftheirnamesarelisted
The patch does not address any of the more important issues I
listed with git-var and git-repo-config in that message.
next prev parent reply other threads:[~2006-02-12 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 21:19 Git 1.1.6.g4d44 make test FAILURE report A Large Angry SCM
2006-02-10 21:38 ` Junio C Hamano
2006-02-11 1:37 ` A Large Angry SCM
2006-02-11 2:17 ` Junio C Hamano
2006-02-11 3:52 ` A Large Angry SCM
2006-02-11 4:14 ` Junio C Hamano
2006-02-11 4:43 ` Junio C Hamano
2006-02-11 12:10 ` [PATCH] Teach repo-config the -l and --get-regexp options Johannes Schindelin
2006-02-12 3:05 ` Junio C Hamano [this message]
2006-02-12 3:14 ` [PATCH] Add support for explicit type specifiers when calling git-repo-config Petr Baudis
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=7vlkwhgtua.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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