From: Peter Harris <git@peter.is-a-geek.org>
To: Rustom Mody <rustompmody@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: about crlf file-encodings and other options
Date: Thu, 16 Jul 2009 11:49:15 -0400 [thread overview]
Message-ID: <eaa105840907160849k7403feffnc3b834e94a33643d@mail.gmail.com> (raw)
In-Reply-To: <f46c52560907160651u1cdc1779r511d227fa5c88956@mail.gmail.com>
On Thu, Jul 16, 2009 at 9:51 AM, Rustom Mody wrote:
> I am trying to figure out the best choices regarding file-encodings,
> crlf choices etc.
> I see some stuff in gitattributes and some in git-config.
>
> So...
> 1. Is there some place I can find out whats the received wisdom
> regarding crlf and file encoding choices
This comes down to personal taste. I actually set core.autocrlf
differently for different projects.
> 2. is there some one place where all the options for all the git
> commands are listed?
>
> For example I find in git-config the following
>
> [branch "devel"]
> remote = origin
> merge = refs/heads/devel
>
> Where does one find out about such options?
"git help config" (those particular ones are under
branch.<name>.remote and branch.<name>.merge).
Peter Harris
prev parent reply other threads:[~2009-07-16 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 13:51 about crlf file-encodings and other options Rustom Mody
2009-07-16 15:49 ` Peter Harris [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=eaa105840907160849k7403feffnc3b834e94a33643d@mail.gmail.com \
--to=git@peter.is-a-geek.org \
--cc=git@vger.kernel.org \
--cc=rustompmody@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;
as well as URLs for NNTP newsgroup(s).