Possible to git rebase to a text file, edit it and then apply from edited file?
up vote
1
down vote
favorite
I have to fix a HUGE history (over 300 messages). Obviously, I will have to rebase to root via git rebase -i --root and then reword all commits that need rewording. So you can get grasp of the scope of this work.
Is there a way to export git history to a file which I can open via sublime (or other text editor), then change commit messages in a more user-friendly manner, and after all changes have been done import changes from this file back into the Git history?
Sci-fi or reality?
git git-rebase git-history
asked Nov 9 at 14:59
sandalone
22.6k51181293
add a comment |
up vote
1
down vote
favorite
I have to fix a HUGE history (over 300 messages). Obviously, I will have to rebase to root via git rebase -i --root and then reword all commits that need rewording. So you can get grasp of the scope of this work.
Is there a way to export git history to a file which I can open via sublime (or other text editor), then change commit messages in a more user-friendly manner, and after all changes have been done import changes from this file back into the Git history?
Sci-fi or reality?
git git-rebase git-history
asked Nov 9 at 14:59
sandalone
22.6k51181293
1
git fast-exportandgit fast-importalready exist and can be made to serve. Otherwise a filter-branch with a map for the new messages.
– jthill
Nov 9 at 15:15
@jthill Does this work on the same repo? Orgit-importhas to be executed onto a new repo?
– sandalone
Nov 9 at 15:23
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have to fix a HUGE history (over 300 messages). Obviously, I will have to rebase to root via git rebase -i --root and then reword all commits that need rewording. So you can get grasp of the scope of this work.
Is there a way to export git history to a file which I can open via sublime (or other text editor), then change commit messages in a more user-friendly manner, and after all changes have been done import changes from this file back into the Git history?
Sci-fi or reality?
git git-rebase git-history
asked Nov 9 at 14:59
sandalone
22.6k51181293
I have to fix a HUGE history (over 300 messages). Obviously, I will have to rebase to root via git rebase -i --root and then reword all commits that need rewording. So you can get grasp of the scope of this work.
Is there a way to export git history to a file which I can open via sublime (or other text editor), then change commit messages in a more user-friendly manner, and after all changes have been done import changes from this file back into the Git history?
Sci-fi or reality?
git git-rebase git-history
git git-rebase git-history
asked Nov 9 at 14:59
sandalone
22.6k51181293
asked Nov 9 at 14:59
sandalone
22.6k51181293
asked Nov 9 at 14:59
sandalone
22.6k51181293
asked Nov 9 at 14:59
sandalone
22.6k51181293
asked Nov 9 at 14:59
sandalone
22.6k51181293
22.6k51181293
1
git fast-exportandgit fast-importalready exist and can be made to serve. Otherwise a filter-branch with a map for the new messages.
– jthill
Nov 9 at 15:15
@jthill Does this work on the same repo? Orgit-importhas to be executed onto a new repo?
– sandalone
Nov 9 at 15:23
add a comment |
1
git fast-exportandgit fast-importalready exist and can be made to serve. Otherwise a filter-branch with a map for the new messages.
– jthill
Nov 9 at 15:15
@jthill Does this work on the same repo? Orgit-importhas to be executed onto a new repo?
– sandalone
Nov 9 at 15:23
1
1
git fast-export and git fast-import already exist and can be made to serve. Otherwise a filter-branch with a map for the new messages.– jthill
Nov 9 at 15:15
git fast-export and git fast-import already exist and can be made to serve. Otherwise a filter-branch with a map for the new messages.– jthill
Nov 9 at 15:15
@jthill Does this work on the same repo? Or
git-import has to be executed onto a new repo?– sandalone
Nov 9 at 15:23
@jthill Does this work on the same repo? Or
git-import has to be executed onto a new repo?– sandalone
Nov 9 at 15:23
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228168%2fpossible-to-git-rebase-to-a-text-file-edit-it-and-then-apply-from-edited-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
git fast-exportandgit fast-importalready exist and can be made to serve. Otherwise a filter-branch with a map for the new messages.– jthill
Nov 9 at 15:15
@jthill Does this work on the same repo? Or
git-importhas to be executed onto a new repo?– sandalone
Nov 9 at 15:23