From: Phil Hord <hordp@cisco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Eric Frederich <eric.frederich@gmail.com>, git@vger.kernel.org
Subject: Re: fast forward a branch from another
Date: Thu, 12 May 2011 12:26:55 -0400 [thread overview]
Message-ID: <4DCC0A4F.7000800@cisco.com> (raw)
In-Reply-To: <7vsjsjdhud.fsf@alter.siamese.dyndns.org>
On 05/12/2011 12:06 PM, Junio C Hamano wrote:
> [...]
> Instead of switching to "stable", while still on the development, you
> could do
>
> $ git push . HEAD:stable
>
> which would succeed only when you are purely ahead of stable (otherwise it
> will fail as you are not forcing).
>
Wow! Another gem. I didn't realize you could use 'dot' to refer to the
same repo you're in.
I don't see this feature listed in the git push [REMOTES] section. Is
it documented somewhere else?
Phil
next prev parent reply other threads:[~2011-05-12 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 14:40 fast forward a branch from another Eric Frederich
2011-05-12 15:31 ` Michael J Gruber
2011-05-12 15:34 ` Michael J Gruber
2011-05-12 16:06 ` Junio C Hamano
2011-05-12 16:26 ` Phil Hord [this message]
2011-05-12 16:49 ` Junio C Hamano
2011-05-12 16:58 ` Phil Hord
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=4DCC0A4F.7000800@cisco.com \
--to=hordp@cisco.com \
--cc=eric.frederich@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).