From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: E R <pc88mxer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: adding files in .git?
Date: Mon, 16 Mar 2009 17:56:32 +0100 [thread overview]
Message-ID: <vpqr60x76f3.fsf@bauges.imag.fr> (raw)
In-Reply-To: <3a69fa7c0903160814u42fbb461qf03a37176546357d@mail.gmail.com> (E. R.'s message of "Mon\, 16 Mar 2009 10\:14\:58 -0500")
E R <pc88mxer@gmail.com> writes:
> 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?
Neither of them will propagate through clone. Depending on your
use-case, this is an advantage or not.
--
Matthieu
prev parent reply other threads:[~2009-03-16 17:03 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
2009-03-16 16:56 ` Matthieu Moy [this message]
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=vpqr60x76f3.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.