From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Philip Oakley <philipoakley@iee.org>
Cc: David <bouncingcats@gmail.com>, Samuel Lijin <sxlijin@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Stefan Beller <sbeller@google.com>,
git@vger.kernel.org
Subject: Re: What does this output of git supposed to mean ?
Date: Tue, 06 Jun 2017 19:38:22 +0530 [thread overview]
Message-ID: <1496758102.6664.2.camel@gmail.com> (raw)
In-Reply-To: <xmqqr2yx8h9v.fsf@gitster.mtv.corp.google.com>
On Tue, 2017-06-06 at 20:52 +0900, Junio C Hamano wrote:
> "Waiting for the initial commit", or "No commits yet", can be
> explained to describe the state of the current branch (not the state
> of the repository), and it is correct that we do not have any commit
> on the branch, and the branch is waiting for the initial commit.
>
Looks descriptive to me too. Just for the note, I wouldn't have asked
this question if `git status` showed a message like this.
--
Regards,
Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
next prev parent reply other threads:[~2017-06-06 14:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 14:04 What does this output of git supposed to mean ? Kaartic Sivaraam
2017-06-05 23:10 ` brian m. carlson
2017-06-05 23:18 ` Stefan Beller
2017-06-06 1:00 ` Junio C Hamano
2017-06-06 1:11 ` brian m. carlson
2017-06-06 1:39 ` Samuel Lijin
2017-06-06 1:52 ` Junio C Hamano
2017-06-06 2:06 ` David
2017-06-06 11:07 ` Philip Oakley
2017-06-06 11:43 ` SZEDER Gábor
2017-06-06 18:42 ` Jeff King
2017-06-06 18:53 ` Jeff King
2017-06-06 11:52 ` Junio C Hamano
2017-06-06 14:08 ` Kaartic Sivaraam [this message]
2017-06-06 22:05 ` Philip Oakley
2017-06-07 12:56 ` Kaartic Sivaraam
2017-06-07 22:14 ` Philip Oakley
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=1496758102.6664.2.camel@gmail.com \
--to=kaarticsivaraam91196@gmail.com \
--cc=bouncingcats@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philipoakley@iee.org \
--cc=sandals@crustytoothpaste.net \
--cc=sbeller@google.com \
--cc=sxlijin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.