From: "David Tweed" <david.tweed@gmail.com>
To: git@vger.kernel.org
Subject: specifying "fast-forward" only in git-pull
Date: Wed, 28 Mar 2007 22:12:31 +0100 [thread overview]
Message-ID: <e1dab3980703281412m78c2481bj9b9f7ec885dbbe4f@mail.gmail.com> (raw)
Hi, I'm looking through the documentation on git-pull and
I see that I can specify a particular (sequence of) merge
strategies, but I can't see a way to say "only do a fast
forward, stopping if a fast forward doesn't apply".
(Fast-forward doesn't appear to be a named strategy,
which is why I can't use it with -s). Is there a way to
do this?
Rationale: I have a repository on several machines that
are synchronised via usb-stick. 99.9% of the time a fast
forward is all that is needed, and for scripting the
synchronisation I'd like to restrict it so that only
fast-forwards can happen automatically and everything
else I have to do by invoking git myself. (Somehow I managed to get
a merge that gave a weird result without me actually
noticing for a couple of days, which combined with
my chronological version scripts seemed to put new
trees onto an unnamed branch. I've got the repo sorted
out now, but I want to avoid the same issue in future.)
Many thanks for any help.
--
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
Details are all that matters; God dwells there, and you never get to
see Him if you don't struggle to get them right. -- Stephen Jay Gould
next reply other threads:[~2007-03-28 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 21:12 David Tweed [this message]
2007-03-28 21:26 ` specifying "fast-forward" only in git-pull Junio C Hamano
2007-03-28 21:30 ` Shawn O. Pearce
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=e1dab3980703281412m78c2481bj9b9f7ec885dbbe4f@mail.gmail.com \
--to=david.tweed@gmail.com \
--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).