From: Lee Griffiths <poddster@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Florian Mickler <florian@mickler.org>, git@vger.kernel.org
Subject: Re: Checking for fast-forward
Date: Wed, 8 Jul 2009 18:36:30 +0100 [thread overview]
Message-ID: <ca4f67be0907081036j38724491n6c4c0e9aa995ee51@mail.gmail.com> (raw)
In-Reply-To: <4A530594.20100@drmicha.warpmail.net>
Thanks for the answers :)
After seeing that git push skips the packing (and potentially other
things) when doing a dry run, and given that:
git push --dry-run
takes 1.5s on average and that:
git fetch
git rev-list master..remotes/origin/master
OR
git ls-remote origin refs/remotes/origin/master
take 4s on average, I think I'll stick with the dry-run & checking for
exception method.
Thanks though :)
2009/7/7 Michael J Gruber <git@drmicha.warpmail.net>:
> If $(git rev-list bar..remotes/origin/foo) is empty then the branch foo
> in the remote repo can be fast-forwarded to bar.
prev parent reply other threads:[~2009-07-08 17:37 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
2009-07-07 11:01 ` Michael J Gruber
2009-07-08 17:36 ` Lee Griffiths [this message]
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=ca4f67be0907081036j38724491n6c4c0e9aa995ee51@mail.gmail.com \
--to=poddster@gmail.com \
--cc=florian@mickler.org \
--cc=git@drmicha.warpmail.net \
--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).