From: Fabian Franz <FabianFranz@gmx.de>
To: git@vger.kernel.org
Subject: [PATCH] git-pasky: Add .gitrc directory to allow command defaults like with .cvsrc
Date: Fri, 22 Apr 2005 18:28:48 +0200 [thread overview]
Message-ID: <200504221828.51752.FabianFranz@gmx.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
one thing I liked about CVS was its way to configure default parameters for
commands.
And as I really like the colored log output, I wanted it as default.
While .cvsrc parsing would be quite expensive, using a directory + files
should be fairly cheap and result just in one additional stat-call.
So I added "-c" to ~/.gitrc/log and some code to parse this.
Index: git
===================================================================
- --- 0a9ee5a4d947b998a7ce489242800b39f98eeee5/git (mode:100755
sha1:39969debd59ed51c57973c819cdcc3ca8a7da819)
+++ uncommitted/git (mode:100755)
@@ -67,6 +67,7 @@
exit 1
fi
+[ -e "$HOME/.gitrc/$cmd" ] && set -- $(cat "$HOME/.gitrc/$cmd") "$@"
case "$cmd" in
"add") gitadd.sh "$@";;
cu
Fabian
PS: Should the commandline parsing be cleaned up or do you want to do that
after first release of cogito? And if yes, do you want to use "getopts" or
would this be not supported on some systems?
PPS: I'm fairly new to git, how do I create a diff with the signed-by fields
and with what do I need to sign it?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFCaSZDI0lSH7CXz7MRAoq8AJwM2lxPfl0ej32WU7q6bh6WIq5+EACgghGn
mvJzbvg6/bxWLFKfsP1ZEeI=
=03wm
-----END PGP SIGNATURE-----
next reply other threads:[~2005-04-22 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 16:28 Fabian Franz [this message]
2005-04-22 16:38 ` [PATCH] git-pasky: Add .gitrc directory to allow command defaults like with .cvsrc 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=200504221828.51752.FabianFranz@gmx.de \
--to=fabianfranz@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