git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: Philip Oakley <philipoakley@iee.org>, Junio C Hamano <gitster@pobox.com>
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: Wed, 7 Jun 2017 18:26:47 +0530	[thread overview]
Message-ID: <2d7e165d-b44c-ab3c-a4db-af5df64048a9@gmail.com> (raw)
In-Reply-To: <4A4DB115A50D432A8FF7B8589C5BAC84@PhilipOakley>

On Wednesday 07 June 2017 03:35 AM, Philip Oakley wrote:
> Maybe have a try at a patch to update the text? See the 
> git/Documentation/SubmittingPatches for guidance.
I guess this should be trivial (correct me if I'm wrong). I'll try when 
I find time. In case I make the change which of the following message 
should replace the message 'Initial commit' ? (this could be a poll, I 
guess)

1. No commit yet
2. Waiting for initial commit
3. Your current branch does not have any commits

Further what is to be done about the following comment,

On Wednesday 07 June 2017 12:23 AM, Jeff King wrote:

There is a slight complication, though. There's similar text in "git 
status -sb", which shows: ## Initial commit on master Should that also 
change to use consistent terminology? If so, we need a phrasing short 
phrasing that matches (and the --porcelain and --porcelain=v2 formats of 
course would need to remain the same).

BTW, could anyone provide a pointer to the implementation that prints 
this message ?

--
Regards,
Kaartic Sivaraam

  reply	other threads:[~2017-06-07 12:56 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
2017-06-06 22:05                     ` Philip Oakley
2017-06-07 12:56                       ` Kaartic Sivaraam [this message]
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=2d7e165d-b44c-ab3c-a4db-af5df64048a9@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 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).