From: Junio C Hamano <gitster@pobox.com>
To: "José Fonseca" <jrfonseca@tungstengraphics.com>
Cc: git@vger.kernel.org
Subject: Re: [RFE/PATCH] git-fetch-rebase
Date: Fri, 14 Dec 2007 15:50:01 -0800 [thread overview]
Message-ID: <7vy7bwomza.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1197670351.21175.33.camel@localhost> (José Fonseca's message of "Fri, 14 Dec 2007 22:12:31 +0000")
José Fonseca <jrfonseca@tungstengraphics.com> writes:
> For those who use git as a better centralized SCM, it became a common
> practice to do git-fetch + git-rebase instead of just git-pull, so that
> the history is linear, instead of being full of tiny merges.
"git pull --rebase"?
next prev parent reply other threads:[~2007-12-14 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 22:12 [RFE/PATCH] git-fetch-rebase José Fonseca
2007-12-14 23:50 ` Junio C Hamano [this message]
2007-12-15 0:37 ` José Fonseca
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=7vy7bwomza.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrfonseca@tungstengraphics.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).