git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Seymour <jon.seymour@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: RFD: best way to automatically rewrite a git DAG as a linear history?
Date: Thu, 18 Feb 2010 13:35:07 +1100	[thread overview]
Message-ID: <2cfc40321002171835j107d2cdcr5f7667d769bf391e@mail.gmail.com> (raw)

Does the git toolset currently support rewriting a restricted git DAG
as a linear history in a completely automated way?

I understand that git rebase --root will attempt to rebase a DAG, but
as far as I can tell any conflicts that occur during the rebase
require a manual intervention to correct. My goal is a completely
automated rewrite.

I guess some might be sceptical that a sane automated rewrite is
impossible, but I am insane enough to think it might actually be
possible.

I have prototype that implements an algorithm that does this [ for a
restricted class of DAG of interest to me ], so I can't be completely
insane, but if other people have already knocked the corners of this
particular wheel, I'd be interested to learn of their efforts.

Regards.

jon

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18  2:35 Jon Seymour [this message]
2010-02-18  5:11 ` RFD: best way to automatically rewrite a git DAG as a linear history? Jeff King
2010-02-18 18:38   ` Avery Pennarun
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=2cfc40321002171835j107d2cdcr5f7667d769bf391e@mail.gmail.com \
    --to=jon.seymour@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).