git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco <netuse@lavabit.com>
To: git@vger.kernel.org
Subject: Re: Why doesn't git commit -a track new files
Date: Thu, 24 Feb 2011 15:20:27 +0100	[thread overview]
Message-ID: <20110224152027.05aed833@glyph> (raw)
In-Reply-To: AANLkTinDT6jBxQZ5eukA6Fa=-xRMJsHTJ4pM+Hz4KER_@mail.gmail.com

On 2011-02-24 Pascal Obry <pascal@obry.net> wrote:

> Marco,
> 
> > 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"
> 
> Never had the need for this. The reason is maybe when you are trying to have
> a small set if incremental commits, you usually don't want to add
> everything but you review the change carefully with "git add -p".

Of course not as default behaviour. Just as a switch (e.g. -A). If one wishes
this behaviour one can use it. Nobody forces you to use it (like -a).

> Now in some circumstances it could probably be useful.

Yes.


Marco

  reply	other threads:[~2011-02-24 14:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 10:22 Why doesn't git commit -a track new files Marco
2011-02-24 14:06 ` Ævar Arnfjörð Bjarmason
2011-02-24 14:09 ` Pascal Obry
2011-02-24 14:20   ` Marco [this message]
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=20110224152027.05aed833@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 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).