Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5966751
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T19:50:40+00:00 2026-05-22T19:50:40+00:00

Git has a bunch of procedures for altering history. ( rebase , filter-branch ,

  • 0

Git has a bunch of procedures for altering history.
(rebase, filter-branch, commit --ammend, guilt, stacked git, etc)

However, it may sometimes be preferable if there was a procedure to turn the last few commits into a file containing a series of patches with the commit metadata, which could be freely edited, and then turned back into a rebased history (assuming the patches still applied).

Does anyone have a way to do this?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T19:50:40+00:00Added an answer on May 22, 2026 at 7:50 pm

    I ended up using magit which solves roughly this problem very well for me.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have a git project which has quite a big history. Specifically, early in
The git autocompletion has show and show-branch but not show-ref . Is this because
Git has a much-touted(?) octopus-merge capability that can merge many heads into one. But
Since Git has the ability to keep track (and keep it clean) of branches
An svn repository I'm mirroring through git-svn has changed URL. In vanilla svn you'd
Some Git commands take commit ranges and one valid syntax is to separate two
Suppose your git history looks like this: 1 2 3 4 5 1–5 are
My git repository has somehow gone wonky - I loaded up msysgit this morning
I have a git directory which contains the a whole bunch of files and
Git has the very handy archive command which allows me to make a copy

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.