git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Removing part of the history

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Nov 28, 2008, 21:34 UTC
Message-ID
<20081128213454.GE19355@genesis.frugalware.org>
In-Reply-To
<49306150.6010701@datacom.ind.br>
On Fri, Nov 28, 2008 at 07:23:28PM -0200, Samuel Lucas Vaz de Mello <samuellucas@datacom.ind.br> wrote:
> There is any way to get rid of the (broken) cvs-old tree?
> 
> I've tried to rebase, but the commits from A' and A are different, it
> tries to reapply all history in CVS.
Have you tried git rebase --onto?
> I've tried to checkout a point before our changes start (B') and then,
> using a script, cherry-pick all commits up to HEAD that are not in
> cvs-old branch. This approach didn't handled well merges between our
> branches (K-L-M and X-Y).
git rebase --preserve-merges is probably what you are searching for.
Previous: Samuel Lucas Vaz de MelloNext: Jakub Narebski
Message 2 of 3 in “Removing part of the history”
  1. Samuel Lucas Vaz de MelloNov 28, 2008
  2. Miklos VajnaNov 28, 2008
  3. Jakub NarebskiNov 28, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.