git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Son Luong Ngoc <sluongng@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [EXT] Re: Filtering commits after filtering the tree
Date: Fri, 31 Dec 2021 18:23:12 +0100	[thread overview]
Message-ID: <9ba1551b-375c-fe71-3402-8a54dbeec085@rz.uni-regensburg.de> (raw)
In-Reply-To: <CAL3xRKet7KXTx+6ALVZCxeFRkU3guwNc6GtAT1iofB=UKqj2fg@mail.gmail.com>

On 12/30/21 2:19 PM, Son Luong Ngoc wrote:
> Hi Ulrich,
> 
> On Thu, Dec 30, 2021 at 12:28 PM Ulrich Windl
> <Ulrich.Windl@rz.uni-regensburg.de> wrote:
>>
>> Hi guys!
>>
>>
>> As  I know there are really smart ones around, please don't laugh how I helped myself with this problem:
>> https://stackoverflow.com/q/70505903/6607497
>> I'm sure you wouldn't have wasted hours with rebasing interactively...
>>
>>
>> Feel free to comment either on the list or at SO (comment or improved answer).
> 
> You probably want to try git-filter-repo (1)
> while using `--message-callback` as documented in (2)

Interestingly in SLES12 SP5 there is a message recommending 
git-filter-repo, but when I had tried "man git-filter-repo" there was no 
manual page. So I did not follow that path...

> 
>>
>>
>> Regards,
>> Urich
>>
>>
> 
> Hope it helps,
> Son Luong.
> 
> (1) https://github.com/newren/git-filter-repo
> (2) https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#CALLBACKS
> 

  reply	other threads:[~2021-12-31 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  9:43 Filtering commits after filtering the tree Ulrich Windl
2021-12-30 13:19 ` Son Luong Ngoc
2021-12-31 17:23   ` Ulrich Windl [this message]
2021-12-31 23:48   ` Elijah Newren
2022-01-03  9:26     ` Antw: [EXT] " Ulrich Windl

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ba1551b-375c-fe71-3402-8a54dbeec085@rz.uni-regensburg.de \
    --to=ulrich.windl@rz.uni-regensburg.de \
    --cc=git@vger.kernel.org \
    --cc=sluongng@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).