All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco <netuse@lavabit.com>
To: git@vger.kernel.org
Subject: Why doesn't git commit -a track new files
Date: Thu, 24 Feb 2011 11:22:46 +0100	[thread overview]
Message-ID: <20110224112246.3f811ac2@glyph> (raw)

Hi,

I'm new to git and a bit confused about how some commands work.

git add .                    -- Adds everything *but* deleted files
git add -A                   -- Adds everything
git commit -a -m "whatever"  -- Commits everything *but* new files

I don't understand why there's not switch (is there?) for commit to commit new
and deleted files, like -A for git add? Is the only thing to do this sth like

git add -A && git commit -m "Message"


Marco

             reply	other threads:[~2011-02-24 10:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 10:22 Marco [this message]
2011-02-24 14:06 ` Why doesn't git commit -a track new files Ævar Arnfjörð Bjarmason
2011-02-24 14:09 ` Pascal Obry
2011-02-24 14:20   ` Marco
2011-02-24 15:02 ` Michael J Gruber
2011-02-24 15:49   ` Jeff King
2011-02-24 15:54     ` Michael J Gruber
2011-02-24 16:00       ` Jeff King
2011-02-24 16:01         ` Michael J Gruber
2011-02-24 16:09           ` Jeff King
2011-02-25  8:51             ` Michael J Gruber
2011-02-25  9:01               ` Jeff King
2011-02-25  9:03                 ` Michael J Gruber
2011-02-25  9:09                   ` Jeff King
2011-02-24 16:04   ` Matthieu Moy
2011-02-24 16:04     ` Michael J Gruber
2011-02-24 16:47       ` Marco
2011-02-25  4:30   ` Miles Bader
2011-02-25  8:43     ` Michael J Gruber
2011-02-26  6:45       ` Miles Bader
2011-02-24 16:19 ` Marc Weber
2011-02-24 17:27 ` Junio C Hamano
2011-02-24 18:45   ` Marco
2011-02-25 10:15     ` Michael J Gruber
2011-02-25 17:00     ` Junio C Hamano

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=20110224112246.3f811ac2@glyph \
    --to=netuse@lavabit.com \
    --cc=git@vger.kernel.org \
    /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.