From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Marko Macek <Marko.Macek@gmx.net>
Cc: "Dmitry Potapov" <dpotapov@gmail.com>,
"Kristian Høgsberg" <krh@redhat.com>,
"Andreas Ericsson" <ae@op5.se>,
"Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
"Wincent Colaiuta" <win@wincent.com>,
"Git Mailing List" <git@vger.kernel.org>,
andyparkins@gmail.com, torvalds@linux-foundation.org
Subject: Re: Question about "git commit -a"
Date: Sun, 7 Oct 2007 17:26:54 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710071724330.4174@racer.site> (raw)
In-Reply-To: <470878CB.2010609@gmx.net>
Hi,
On Sun, 7 Oct 2007, Marko Macek wrote:
> Dmitry Potapov wrote:
> > You don't. Even with 'commit -a' there is no guarantee that the
> > result will compile, because you can forget to add a new file.
>
> Actually, it would be a good idea for commit to report an error if there
> are any new files that have not been 'added' or 'ignored' (or even if
> there are missing files that have not been 'deleted'.
It is no error.
And it is reported. That is the whole _point_ of having git status output
both changed-but-not-staged and untracked files.
Of course, you only see that when you do not provide the message within
the editor, but from the command line. But then chances are that your
message is too short anyway.
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-07 16:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 15:38 Question about "git commit -a" Paolo Ciarrocchi
2007-10-04 15:43 ` Matthieu Moy
2007-10-04 15:48 ` Paolo Ciarrocchi
2007-10-04 15:58 ` Wincent Colaiuta
2007-10-04 20:33 ` Nguyen Thai Ngoc Duy
2007-10-04 21:10 ` Johannes Schindelin
2007-10-04 21:16 ` Nguyen Thai Ngoc Duy
2007-10-04 21:26 ` Shawn O. Pearce
2007-10-05 8:39 ` Paolo Ciarrocchi
2007-10-05 8:52 ` Andreas Ericsson
2007-10-05 9:06 ` Paolo Ciarrocchi
2007-10-05 10:02 ` Andreas Ericsson
2007-10-05 10:11 ` Matthieu Moy
2007-10-05 10:14 ` Andreas Ericsson
2007-10-05 11:35 ` Matthieu Moy
2007-10-05 12:17 ` Andreas Ericsson
2007-10-05 12:19 ` Paolo Ciarrocchi
2007-10-05 12:23 ` Andreas Ericsson
2007-10-05 12:45 ` Matthieu Moy
2007-10-05 15:56 ` Kristian Høgsberg
2007-10-05 16:33 ` Matthieu Moy
2007-10-05 18:16 ` Marko Macek
2007-10-06 7:43 ` Andy Parkins
2007-10-06 16:13 ` Linus Torvalds
2007-10-07 12:26 ` Wincent Colaiuta
2007-10-05 21:10 ` Dmitry Potapov
2007-10-07 6:12 ` Marko Macek
2007-10-07 14:50 ` Dmitry Potapov
2007-10-07 16:26 ` Johannes Schindelin [this message]
2007-10-05 10:48 ` Wincent Colaiuta
2007-10-04 21:25 ` Andy Parkins
2007-10-05 6:04 ` Miles Bader
2007-10-04 22:34 ` David Soria
2007-10-04 23:03 ` Alex Riesen
2007-10-04 23:19 ` Johannes Schindelin
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=Pine.LNX.4.64.0710071724330.4174@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=Marko.Macek@gmx.net \
--cc=ae@op5.se \
--cc=andyparkins@gmail.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=krh@redhat.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=pclouds@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=win@wincent.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).