git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <ttaylorr@github.com>
To: Mark Wartman <markwartman1@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git Question
Date: Sat, 31 Mar 2018 23:15:22 -0400	[thread overview]
Message-ID: <20180401031522.GA80891@syl.local> (raw)
In-Reply-To: <15759EC4-0867-44B3-995D-6EC121A6EC4C@gmail.com>

On Sat, Mar 31, 2018 at 09:06:53PM -0500, Mark Wartman wrote:
> I saw this pretty exhaustive .gitignore list that a GitHub Help page
> linked to: 9257657 <https://gist.github.com/octocat/9257657> .  Are
> these configurations from the list something one should install on the
> User/global level, or do you recommend managing it in each and every
> project repository?

If those appear helpful for your project(s), then sure; but this is up
to you.

> Concerning these items below, when I said I get these when running a:
> git config —list
>
> credential.helper-osxkeychain
> filter.lfs.clean=git=lfs clean — %f
> filter.lfs.smudge=git-lfs smudge — %f
> filter.lfs.process=git-lfs filter-process
> filter.lfs.required=true
>
> I suspect that the GitHub GUI tool has installed them.  Do you find
> that possible?  I ask because I did not write them.

Yes, I believe that GitHub Desktop runs 'git lfs install', which adds
these to your configuration.


Thanks,
Taylor

  parent reply	other threads:[~2018-04-01  3:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  1:49 Git Question Mark Wartman
2018-03-29  1:58 ` Taylor Blau
     [not found]   ` <15759EC4-0867-44B3-995D-6EC121A6EC4C@gmail.com>
2018-04-01  3:15     ` Taylor Blau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-20 21:28 GIT Question Draggs, Tori
2016-01-22 16:51 ` Johannes Schindelin
     [not found]   ` <1E23015B9294604195E5EBA53602E115FCF59F@WDC-VMAILBOXP25.smrcy.com>
2016-01-22 17:08     ` Johannes Schindelin
2016-01-22 17:22       ` Draggs, Tori
2016-01-22 17:58         ` Santiago Torres

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=20180401031522.GA80891@syl.local \
    --to=ttaylorr@github.com \
    --cc=git@vger.kernel.org \
    --cc=markwartman1@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).