From: Junio C Hamano <gitster@pobox.com>
To: "Ping Yin" <pkufranky@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Any command to simplify 'git fetch origin && git reset --hard origin/master'?
Date: Fri, 18 Jan 2008 23:06:42 -0800 [thread overview]
Message-ID: <7vr6ge9tvh.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <46dff0320801182122t1581b366yad123407aaad6326@mail.gmail.com> (Ping Yin's message of "Sat, 19 Jan 2008 13:22:31 +0800")
"Ping Yin" <pkufranky@gmail.com> writes:
> I often encounter the case that the origin reposotory is rebased and i
> make sure i want to use the origin head as my master
> Now I have to do
> $ git fetch origin && git reset --hard origin/master
The fact you are resetting means you do not have anything
interesting in your own branch yourself (--hard will lose your
changes and you are willing to lose it), which makes the use
case much less interesting, but I can understand a workflow that
is based around rebases, as in:
$ git fetch origin && git rebase origin/master
which would be an equivalent to the resetting --hard when you do
not have anything interesting in your branch but if you do have
interesting commits they will be transplanted on top of the
rebased upstream head.
Upcoming 1.5.4 will have "git pull --rebase origin", which is a
short-hand for the above command. That is a parallel for rebase
based workflow, just like "git pull origin" is a short-hand for
$ git fetch origin && git merge origin/master
to help merge based workflow.
next prev parent reply other threads:[~2008-01-19 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 5:22 Any command to simplify 'git fetch origin && git reset --hard origin/master'? Ping Yin
2008-01-19 6:04 ` David Symonds
2008-01-19 7:06 ` Junio C Hamano [this message]
2008-01-19 8:03 ` Ping Yin
2008-01-19 8:06 ` Junio C Hamano
2008-01-19 8:08 ` Ping Yin
2008-01-19 11:15 ` Johannes Schindelin
2008-01-19 14:03 ` Ping Yin
2008-01-19 22:50 ` Johannes Schindelin
2008-01-20 8:51 ` Ping Yin
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=7vr6ge9tvh.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pkufranky@gmail.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).