git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Stephen Haberman <stephen@exigencecorp.com>
Cc: git@vger.kernel.org
Subject: Re: rebasing merges
Date: Tue, 23 Sep 2008 08:09:23 +0200	[thread overview]
Message-ID: <48D88813.9060400@viscovery.net> (raw)
In-Reply-To: <20080922231927.ef18f420.stephen@exigencecorp.com>

Stephen Haberman schrieb:
> I noticed the t3400.sh test explicitly tests for the flattening
> behavior, but I can't tell if that is because it's testing for
> explicitly desired behavior or if the "linear-izing" is something
> that is up for debate (or a command line/config option).

This is the expected behavior and not up for debate.

Consider this use-case, for example: You keep a private patch or two on
top of upstream, and you also regularly pull from upstream. You get this
history:

  ---o--o--o--o--o--o    <-- origin
      \     \        \
       A--B--M--------N  <-- master

A and B are the private patches. From time to time you want to update them
if they get out of date, which is indicated by merge conflicts in the
merges M and N. Then you want this result:

  ---o--o--o--o--o--o         <-- origin
                     \
                      A'--B'  <-- master

i.e. linearized history without merges.

-- Hannes

  reply	other threads:[~2008-09-23  6:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 20:57 rebasing merges Stephen Haberman
2008-09-23  4:19 ` Stephen Haberman
2008-09-23  6:09   ` Johannes Sixt [this message]
2008-09-23  7:30     ` Samuel Tardieu
2008-09-23  7:52       ` Johannes Sixt
2008-09-23  8:06       ` Andreas Ericsson
2008-09-23  7:46     ` Stephen Haberman
2008-09-23  8:00       ` Johannes Sixt
2008-09-23  8:20       ` Andreas Ericsson
2008-09-23  9:03         ` Stephen Haberman
2008-09-23  9:11           ` Andreas Ericsson
2008-09-23  9:30             ` Stephen Haberman
2008-09-23 18:29               ` Stephen Haberman
2008-09-23 11:16             ` SZEDER Gábor

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=48D88813.9060400@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=stephen@exigencecorp.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).