From: Junio C Hamano <gitster@pobox•com>
To: Sidhant Sharma <tigerkid001@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: [RFC] git subcommand to check if branch is up-to-date with upstream
Date: Mon, 25 Jul 2016 09:58:52 -0700 [thread overview]
Message-ID: <xmqqd1m17iyb.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <57960CFF.5060104@gmail.com> (Sidhant Sharma's message of "Mon, 25 Jul 2016 18:28:39 +0530")
Sidhant Sharma <tigerkid001@gmail•com> writes:
> I was wondering if it would be a good idea to have a command to check if a
> push or pull is required. Perhaps it can also suggest if changes are
> fast-forward or the branches (local and remote) have diverged.
Doesn't "branch -v" give that information these days? You'd need to
"fetch" first to get the up-to-date worldview before running it, of
course.
next prev parent reply other threads:[~2016-07-25 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 12:58 [RFC] git subcommand to check if branch is up-to-date with upstream Sidhant Sharma
2016-07-25 16:58 ` Junio C Hamano [this message]
2016-07-25 17:33 ` Jakub Narębski
2016-07-26 9:32 ` Sidhant Sharma
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=xmqqd1m17iyb.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=tigerkid001@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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