From: "Shawn O. Pearce" <spearce@spearce.org>
To: E R <pc88mxer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: adding files in .git?
Date: Mon, 16 Mar 2009 08:18:23 -0700 [thread overview]
Message-ID: <20090316151823.GP22920@spearce.org> (raw)
In-Reply-To: <3a69fa7c0903160814u42fbb461qf03a37176546357d@mail.gmail.com>
E R <pc88mxer@gmail.com> wrote:
> I'd like to add a "short description" attribute to my .git repository.
> This would be used by my bash prompt setting function in creating the
> PS1 string. How would you recommend that this be implemented?
>
> My ideas are:
>
> 1) Use another file in .git similar to the "description" file (such as
> .git/short-description)
> 2) Use a setting in the .git/config file.
>
> Any comments on the advantages/disadvantages of these approaches? Or
> is there yet another better way?
Using another file may be faster to execute as you can probably
read the file directly in shell, vs. needing to fork to read the
file with `git config`.
But there really isn't a huge argument either way other than that.
--
Shawn.
next prev parent reply other threads:[~2009-03-16 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 15:14 adding files in .git? E R
2009-03-16 15:18 ` Shawn O. Pearce [this message]
2009-03-16 16:56 ` Matthieu Moy
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=20090316151823.GP22920@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=pc88mxer@gmail.com \
/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