From: Andrey Borzenkov <arvidjaar@mail.ru>
To: git@vger.kernel.org
Subject: git commit error on initial (the very first) commit
Date: Sun, 29 Jan 2006 20:26:54 +0300 [thread overview]
Message-ID: <200601292026.54893.arvidjaar@mail.ru> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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'
usage: git-diff-index [-m] [--cached] [<common diff options>] <tree-ish>
[<path>...]
common diff options:
... etc
Committing initial tree 4c9bc57b6911db86c7ab482cca33948a9ba20ef0
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD3PreR6LMutpd94wRAiP1AJwI93tNjyQ3PYjuwh/EP/GQJHhjKQCeNsuq
6oWKT+2XHaU3Qe50hkmkQ+g=
=493D
-----END PGP SIGNATURE-----
next reply other threads:[~2006-01-29 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 17:26 Andrey Borzenkov [this message]
2006-01-29 18:16 ` git commit error on initial (the very first) commit J. Bruce Fields
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=200601292026.54893.arvidjaar@mail.ru \
--to=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).