From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: git@vger.kernel.org
Subject: Re: git commit error on initial (the very first) commit
Date: Sun, 29 Jan 2006 13:16:25 -0500 [thread overview]
Message-ID: <20060129181625.GA5540@fieldses.org> (raw)
In-Reply-To: <200601292026.54893.arvidjaar@mail.ru>
On Sun, Jan 29, 2006 at 08:26:54PM +0300, Andrey Borzenkov wrote:
> May be I do something wrong? What is correct procedure to initially import
> tree? git 1.1.4
>
> {pts/0}% git init-db
> defaulting to local storage area
> {pts/0}% git add .
> {pts/0}% git commit -m 'initial import'
It needs to know which paths to update. Probably you want to include
all the files you added with the "git add", and you can do that just
with -a:
git commit -a -m "initial import"
should do the job. The default commit command for me is usually just
git commit -a.
--b.
next prev parent reply other threads:[~2006-01-29 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 17:26 git commit error on initial (the very first) commit Andrey Borzenkov
2006-01-29 18:16 ` J. Bruce Fields [this message]
2006-01-29 21:08 ` Junio C Hamano
2006-01-29 21:51 ` J. Bruce Fields
2006-01-29 21:05 ` 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=20060129181625.GA5540@fieldses.org \
--to=bfields@fieldses.org \
--cc=arvidjaar@mail.ru \
--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).