From: Francis Galiegue <fge@one2team.com>
To: Mark Burton <markb@ordern.com>
Cc: git@vger.kernel.org
Subject: Re: Git commit won't add an untracked file given on the command line
Date: Tue, 18 Nov 2008 22:27:19 +0100 [thread overview]
Message-ID: <200811182227.20076.fge@one2team.com> (raw)
In-Reply-To: <20081118211237.234d8035@crow>
Le Tuesday 18 November 2008 22:12:37 Mark Burton, vous avez écrit :
> Hi,
>
> When I try:
>
> git commit -m "New file." .gitignore
>
> Where .gitignore is not yet tracked, I get:
>
> error: pathspec '.gitignore' did not match any file(s) known to git.
>
> Is that result by design, sloth or bug (or me being stupid)?
>
You must "git add .gitignore" first. And yes, this is by design.
You could also have done git commit -a -m "themessage".
--
Francis Galiegue
ONE2TEAM
Ingénieur système
Mob : +33 (0) 6 83 87 78 75
Tel : +33 (0) 1 78 94 55 52
fge@one2team.com
40 avenue Raymond Poincaré
75116 Paris
next prev parent reply other threads:[~2008-11-18 21:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 21:12 Git commit won't add an untracked file given on the command line Mark Burton
2008-11-18 21:27 ` Francis Galiegue [this message]
2008-11-18 21:47 ` Mark Burton
2008-11-19 1:07 ` Johannes Schindelin
2008-11-19 1:21 ` Miles Bader
2008-11-19 1:39 ` Johannes Schindelin
2008-11-19 3:43 ` Miles Bader
2008-11-19 9:41 ` Johannes Schindelin
2008-11-20 5:06 ` Miles Bader
2008-11-19 1:51 ` Junio C Hamano
2008-11-19 9:54 ` Mark Burton
2008-11-19 11:27 ` Johannes Schindelin
2008-11-19 13:22 ` Junio C Hamano
2008-11-19 14:41 ` Mark Burton
2008-11-19 18:01 ` Daniel Barkalow
2008-11-19 23:07 ` Junio C Hamano
2008-11-19 23:30 ` Mark Burton
2008-11-19 23:51 ` Junio C Hamano
2008-11-19 23:52 ` Daniel Barkalow
2008-11-20 0:36 ` Junio C Hamano
2008-11-20 10:18 ` David Aguilar
2008-11-18 22:16 ` Matthieu Moy
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=200811182227.20076.fge@one2team.com \
--to=fge@one2team.com \
--cc=git@vger.kernel.org \
--cc=markb@ordern.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