From: Shawn Pearce <spearce@spearce.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: branch.pu.forcefetch
Date: Thu, 28 Dec 2006 23:31:57 -0500 [thread overview]
Message-ID: <20061229043157.GB12072@spearce.org> (raw)
In-Reply-To: <1167363263.15189.79.camel@dv>
Pavel Roskin <proski@gnu.org> wrote:
> Just a random idea - if fast-forward fails, save the original head
> somewhere under refs as a backup. It's like "patch" saving *.orig files
> if there is any doubt that the patch was applied cleanly.
That's the entire point of the reflog. :-)
--
Shawn.
prev parent reply other threads:[~2006-12-29 4:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 20:31 branch.pu.forcefetch Pavel Roskin
2006-12-27 21:14 ` branch.pu.forcefetch Jakub Narebski
2006-12-27 21:14 ` branch.pu.forcefetch Junio C Hamano
2006-12-27 21:20 ` branch.pu.forcefetch Jakub Narebski
2006-12-28 21:29 ` branch.pu.forcefetch Pavel Roskin
2006-12-28 22:44 ` branch.pu.forcefetch Junio C Hamano
2006-12-29 0:32 ` [PATCH 1/2] core.logallrefupdates: log remotes/ tracking branches Junio C Hamano
2006-12-29 0:32 ` [PATCH 2/2] Allow non-fast-forward of remote tracking branches in default clone Junio C Hamano
2006-12-29 4:35 ` Shawn Pearce
2006-12-29 16:39 ` Johannes Schindelin
2006-12-29 1:22 ` branch.pu.forcefetch Pavel Roskin
2006-12-29 2:30 ` branch.pu.forcefetch Junio C Hamano
2006-12-29 3:34 ` branch.pu.forcefetch Pavel Roskin
2006-12-29 4:31 ` Shawn Pearce [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=20061229043157.GB12072@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.