git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Jon Seymour <jon.seymour@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: RFD: best way to automatically rewrite a git DAG as a linear  history?
Date: Thu, 18 Feb 2010 13:38:49 -0500	[thread overview]
Message-ID: <32541b131002181038x26093e3em250b46b5a6e9d97c@mail.gmail.com> (raw)
In-Reply-To: <20100218051129.GD10970@coredump.intra.peff.net>

On Thu, Feb 18, 2010 at 12:11 AM, Jeff King <peff@peff.net> wrote:
> One simple strategy would be to squash all side-branch development into
> a single commit.

Something like this (replace MY_START_BRANCH with your starting
branch, and do this in a clone of your repository so you don't destroy
anything by accident):

        parent=""
        git rev-list --first-parent --reverse  | while read commit; do
                if [ -z "$parent" ]; then
                        git checkout -f $commit
                        git clean -fdx
                else
                        git diff $parent $commit | git apply --index
                        git commit -C $commit
                fi
                parent=$commit
        done

Have fun,

Avery

  reply	other threads:[~2010-02-18 18:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18  2:35 RFD: best way to automatically rewrite a git DAG as a linear history? Jon Seymour
2010-02-18  5:11 ` Jeff King
2010-02-18 18:38   ` Avery Pennarun [this message]
2010-02-19  1:04   ` Jon Seymour
2010-02-19  3:13     ` Avery Pennarun
2010-02-19  7:29       ` Jon Seymour
2010-02-19 20:20         ` Avery Pennarun
2010-02-20  2:25           ` Jon Seymour
2010-02-20  3:05             ` Avery Pennarun
2010-02-21 23:04               ` Jon Seymour
2010-02-21 23:18                 ` Jon Seymour

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=32541b131002181038x26093e3em250b46b5a6e9d97c@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jon.seymour@gmail.com \
    --cc=peff@peff.net \
    /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).