From: Nicolas Vilz <niv@iaglans.de>
To: Sean <seanlkml@sympatico.ca>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, Theodore Tso <tytso@mit.edu>
Subject: Re: git-PS1 bash prompt setting
Date: Sun, 26 Nov 2006 16:05:23 +0100 [thread overview]
Message-ID: <20061126150523.GB18828@hermes.lan.home.vilz.de> (raw)
In-Reply-To: <20061126094212.fde8cce7.seanlkml@sympatico.ca>
On Sun, Nov 26, 2006 at 09:42:12AM -0500, Sean wrote:
> On Sun, 26 Nov 2006 15:27:07 +0100 (CET)
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
> > But there really is no good place to put it: most commands need a git
> > repository, and those which do not, are inappropriate to put an option
> > "--show-ps1" into. Except maybe repo-config. Thoughts?
>
> What about just making it an option to the git wrapper?
I glued that in my system bashrc with the extension, that it shows to me
user.email out of repo-config, which is also very handy. So I am always
reminded to set my user.credentials in .git/config and i always know which
role i play in the repository i am working at.
next prev parent reply other threads:[~2006-11-26 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 18:01 git-PS1 bash prompt setting Sean
2006-11-16 18:35 ` Junio C Hamano
2006-11-26 14:27 ` Johannes Schindelin
2006-11-26 14:42 ` Sean
2006-11-26 15:18 ` Johannes Schindelin
[not found] ` <20061126094212.fde8cce7.seanlkml@sympatico.ca>
2006-11-26 15:05 ` Nicolas Vilz [this message]
2006-11-27 8:48 ` Junio C Hamano
2006-11-27 10:50 ` Nicolas Vilz
2006-11-27 6:54 ` Shawn Pearce
2006-11-27 7:49 ` Jakub Narebski
2006-11-27 12:56 ` Sean
[not found] ` <20061127075650.81a5a850.seanlkml@sympatico.ca>
2006-11-27 17:02 ` Shawn Pearce
2006-11-27 17:38 ` Sean
[not found] <20061116130111.921396df.seanlkml@sympatico.ca>
2006-11-17 8:38 ` Nicolas Vilz
2006-11-17 9:20 ` Sean
2006-11-19 6:28 ` Junio C Hamano
[not found] ` <20061117042051.d2fbddb6.seanlkml@sympatico.ca>
2006-11-17 9:52 ` Nicolas Vilz
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=20061126150523.GB18828@hermes.lan.home.vilz.de \
--to=niv@iaglans.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
--cc=tytso@mit.edu \
/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).