From: NGUYEN Huynh Khoi Nguyen <nguyenhu@ensimag.imag.fr>
To: git@vger.kernel.org
Cc: Matthieu.Moy@grenoble-inp.fr,
NGUYEN Huynh Khoi Nguyen <nguyenhu@ensibm.imag.fr>
Subject: [PATCH 2/2] Test File Name: t1306-second-config-file.sh
Date: Fri, 25 May 2012 21:47:19 +0200 [thread overview]
Message-ID: <1337975239-17169-2-git-send-email-nguyenhu@ensibm.imag.fr> (raw)
In-Reply-To: <1337975239-17169-1-git-send-email-nguyenhu@ensibm.imag.fr>
There are 4 tests:
test1 and test2: read tests
test1: ~/.config/git/config exists and ~/.gitconfig doesn't
git reads ~/.config/git/config
test2: ~/.config/git/config exists and ~/.gitconfig exists
git reads ~/.gitconfig
test3 and test4: write tests
test3: ~/.config/git/config exists and ~/.gitconfig doesn't
git writes in ~/.config/git/config
test4: ~/.config/git/config exists and ~/.gitconfig exists
git writes in ~/.gitconfig
---
t/t1306-second-config-file.sh | 47 +++++++++++++++++++++++++++++++++++++++++
1 files changed, 47 insertions(+), 0 deletions(-)
create mode 100755 t/t1306-second-config-file.sh
diff --git a/t/t1306-second-config-file.sh b/t/t1306-second-config-file.sh
new file mode 100755
index 0000000..5406456
--- /dev/null
+++ b/t/t1306-second-config-file.sh
@@ -0,0 +1,47 @@
+#!/bin/sh
+#
+# Copyright (c) 2012 Valentin Duperray, Lucien Kong, Franck Jonas,
+# Thomas Nguy, Khoi Nguyen
+# Grenoble INP Ensimag
+#
+
+test_description='~/.config/git/config instead of ~/.gitconfig'
+
+. ./test-lib.sh
+
+test_expect_success 'read: ~/.config/git/config exists and ~/.gitconfig doesn'\''t' '
+ mkdir .config &&
+ mkdir .config/git &&
+ echo "[user]" >.config/git/config &&
+ echo " name = read_config" >>.config/git/config &&
+ echo read_config >expect &&
+ git config --global --get user.name >output &&
+ test_cmp expect output
+'
+
+test_expect_success 'read: ~/.config/git/config exists and ~/.gitconfig exists' '
+ >.gitconfig &&
+ echo "[user]" >.gitconfig &&
+ echo " name = read_gitconfig" >>.gitconfig &&
+ echo read_gitconfig >expect &&
+ git config --global --get user.name >output &&
+ test_cmp expect output
+'
+
+test_expect_success 'write: ~/.config/git/config exists and ~/.gitconfig doesn'\''t' '
+ rm .gitconfig &&
+ git config --global user.name "write_config" &&
+ echo "[user]" >expect &&
+ echo " name = write_config" >>expect &&
+ test_cmp expect .config/git/config
+'
+
+test_expect_success 'write: ~/.config/git/config exists and ~/.gitconfig exists' '
+ >.gitconfig &&
+ git config --global user.name "write_gitconfig" &&
+ echo "[user]" >expect &&
+ echo " name = write_gitconfig" >>expect &&
+ test_cmp expect .gitconfig
+'
+
+test_done
--
1.7.0.4
next prev parent reply other threads:[~2012-05-25 20:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 19:47 [PATCH 1/2] Add possibility to store configuration in ~/.config/git/config file NGUYEN Huynh Khoi Nguyen
2012-05-25 19:47 ` NGUYEN Huynh Khoi Nguyen [this message]
2012-05-25 20:30 ` Jeff King
2012-05-25 21:25 ` Junio C Hamano
2012-05-25 21:44 ` Jeff King
2012-05-26 10:15 ` Nguyen Thai Ngoc Duy
2012-05-26 21:54 ` Jeff King
2012-05-28 21:05 ` David Aguilar
2012-05-26 9:05 ` Matthieu Moy
2012-05-25 21:26 ` jaseem abid
2012-05-26 8:53 ` Matthieu Moy
2012-05-26 21:49 ` Jeff King
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=1337975239-17169-2-git-send-email-nguyenhu@ensibm.imag.fr \
--to=nguyenhu@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=nguyenhu@ensibm.imag.fr \
/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).