From: Florian Mickler <florian@mickler.org>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Lee Griffiths <poddster@gmail.com>, git@vger.kernel.org
Subject: Re: Checking for fast-forward
Date: Tue, 7 Jul 2009 12:46:57 +0200 [thread overview]
Message-ID: <20090707124657.1b0fe4df@schatten> (raw)
In-Reply-To: <4A530594.20100@drmicha.warpmail.net>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
On Tue, 07 Jul 2009 10:21:40 +0200
Michael J Gruber <git@drmicha.warpmail.net> wrote:
> If $(git rev-list bar..remotes/origin/foo) is empty then the branch
> foo in the remote repo can be fast-forwarded to bar.
>
> Chhers,
> Michael
in that case you could also do
'git cherry bar origin/foo'
that shows you all commits that are in origin/foo but not in bar.
Sincerely,
Florian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-07-07 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ca4f67be0907060936v7bf7c44y4395717fff854fd4@mail.gmail.com>
2009-07-06 21:26 ` Checking for fast-forward Florian Mickler
2009-07-07 8:21 ` Michael J Gruber
2009-07-07 10:46 ` Florian Mickler [this message]
2009-07-07 11:01 ` Michael J Gruber
2009-07-08 17:36 ` Lee Griffiths
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=20090707124657.1b0fe4df@schatten \
--to=florian@mickler.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=poddster@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).