All of lore.kernel.org
 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: Wed, 28 Mar 2018 18:58:48 -0700	[thread overview]
Message-ID: <20180329015848.GA82123@syl.local> (raw)
In-Reply-To: <CA263ADB-E23D-4C75-ACDC-C9C0B75A4A85@gmail.com>

On Wed, Mar 28, 2018 at 08:49:19PM -0500, Mark Wartman wrote:
> I am following this tutorial and I expected to only see user.name &
> user.email, so what are the filters.lfs’s and the credential.helper?
> Should I ignore them, or try to get rid of them?  Please advise.

The `filter.lfs` configuration is set by Git LFS [1] in order to
correctly filter large files into your working copy.

You can safely ignore these, or remove them if you are not using Git
LFS.

> What is the best way to upgrade to a newer stable version of git?

On macOS, you can use Homebrew [2] to install any version of Git.
Install the latest via:

  brew update && brew install git

Thanks,
Taylor

[1]: https://git-lfs.github.com
[2]: https://brew.sh

  reply	other threads:[~2018-03-29  1:58 UTC|newest]

Thread overview: 31+ 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 [this message]
     [not found]   ` <15759EC4-0867-44B3-995D-6EC121A6EC4C@gmail.com>
2018-04-01  3:15     ` Taylor Blau
  -- 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
2012-02-02 19:41 git question Mark Hounschell
2012-02-02 19:49 ` Jack Stone
2012-02-02 19:57   ` Mark Hounschell
2012-01-23 23:02 chromaticwt zac
2012-01-24  5:11 ` Tirtha Ghosh
2011-12-21  9:19 [can-utils] canbusload: flush output at the end of each cycle Kurt Van Dijck
2011-12-22  6:40 ` Oliver Hartkopp
2012-01-11 11:12   ` Marc Kleine-Budde
2012-01-11 11:18     ` git question Kurt Van Dijck
2012-01-11 11:28       ` Marc Kleine-Budde
2012-01-11 12:22         ` Kurt Van Dijck
2010-08-14  9:25 Stefan Kuhne
2010-08-14 11:11 ` Vincent Hanquez
2010-08-14 13:15   ` Stefan Kuhne
2010-08-14 14:16     ` Pasi Kärkkäinen
2010-08-14 14:22       ` Stefan Kuhne
2010-08-14 19:34         ` Daniel Stodden
2010-08-16 11:55         ` Josip Rodin
2010-08-16 16:06           ` Konrad Rzeszutek Wilk
2006-02-14 10:04 Jes Sorensen
2006-02-14 13:12 ` Jes Sorensen
2006-02-14 16:56 ` Luck, Tony
2006-02-28  9:51 ` Jes Sorensen
2006-02-28 15:22 ` Luck, Tony
2006-02-28 15:45 ` Jes Sorensen
2006-02-28 15:51 ` Luck, Tony

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=20180329015848.GA82123@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 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.