From: Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
"git@vger.kernel.org List" <git@vger.kernel.org>,
Yuval Kogman <nothingmuch@woobling.org>,
Sverre Hvammen Johansen <hvammen@gmail.com>
Subject: Re: I want "fast forward my workdir to upstream if it's safe"
Date: Mon, 11 May 2009 22:11:31 +0200 [thread overview]
Message-ID: <EDAB1A7F-628A-47F6-BAEB-89935E86546A@orakel.ntnu.no> (raw)
In-Reply-To: <7vk54rvb8x.fsf@alter.siamese.dyndns.org>
On 8. mai. 2009, at 17.57, Junio C Hamano wrote:
> Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no> writes:
>
>> I read it as a request for pull/merge --ff-only (based on "abort if
>> the workdir is dirty or is not a fast-forward update"). This feature
>> has been implemented twice, but never included:
>
> Interesting. Do you mean twice they were both found lacking,
> substandard,
> useless, uninteresting, buggy, incorrect, or all of the above? Or
> was it
> just somebody simply forgot to apply a perfect patchset twice?
Sorry, I should have summarised.
I guess Yuval explained what happened to his patch himself. Sverre's
was dropped after a fair amount of discussion and several rounds, but
his series added multiple fast-forward strategies, not just "ff-only".
The last reference I can find to it in the archives is Dscho asking
for the feature to be held off pending the builtinification of git-
merge (http://article.gmane.org/gmane.comp.version-control.git/
82623). Sverre probably lost interest in following up after that.
It looks like there's some interest behind the "--ff=only" feature
now, at least. I remembered the thread because of it; I wanted to
replace a "git reset --hard" in my workflow with something slightly
safer, and --ff=only would have fit.
--
Eyvind Bernhardsen
next prev parent reply other threads:[~2009-05-11 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 21:40 I want "fast forward my workdir to upstream if it's safe" Randal L. Schwartz
2009-05-07 23:18 ` Wincent Colaiuta
2009-05-07 23:20 ` Randal L. Schwartz
2009-05-08 2:30 ` Jeff King
2009-05-08 6:53 ` Andreas Ericsson
2009-05-08 7:01 ` Jeff King
2009-05-08 12:34 ` Eyvind Bernhardsen
2009-05-08 14:02 ` Randal L. Schwartz
2009-05-08 15:57 ` Junio C Hamano
2009-05-08 16:15 ` Jakub Narebski
2009-05-11 20:11 ` Eyvind Bernhardsen [this message]
2009-05-08 21:34 ` Miles Bader
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EDAB1A7F-628A-47F6-BAEB-89935E86546A@orakel.ntnu.no \
--to=eyvind-git@orakel.ntnu.no \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvammen@gmail.com \
--cc=merlyn@stonehenge.com \
--cc=nothingmuch@woobling.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).