git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Alex Radulescu <mydesweb@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: git commit -a -m is not working
Date: Mon, 28 Sep 2015 10:11:32 -0700	[thread overview]
Message-ID: <20150928171132.GA11993@google.com> (raw)
In-Reply-To: <20150926185416.GA233088@vauxhall.crustytoothpaste.net>

Hi,

brian m. carlson wrote:
> On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:

>> Alex:testGit Alex$ git commit -a -m 'made a change'
>>
>> On branch v1.0
>>
>> Untracked files:
>>
>> new_branch.txt
>>
>> nothing added to commit but untracked files present
>
> git commit -a does not add untracked files.  Such files might be build
> by-products or such and you haven't told Git to track them, so it
> doesn't.

You can run "git add -N <files>" to tell Git to start caring about
some new files (e.g., "git add -N ." to track them all).

Alternatively, you can run "git add <files>" to tell Git that the
current content of those files is ready for commit (e.g., "git add ."
before "git status" and "git commit" to commit everything).

More details are at http://jk.gs/gittutorial.html#_making_changes
(also available by running "git help tutorial").

Thanks and hope that helps,
Jonathan

  reply	other threads:[~2015-09-28 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-26 18:51 git commit -a -m is not working Alex Radulescu
2015-09-26 18:54 ` brian m. carlson
2015-09-28 17:11   ` Jonathan Nieder [this message]
2015-09-28 23:34     ` Alex Radulescu

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=20150928171132.GA11993@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mydesweb@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    /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).