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

Re: rebase-with-history -- a technique for rebasing without trashing your repo history

From
AKAbderrahim Kitouni <a.kitouni@gmail.com>
Date
Aug 13, 2009, 20:31 UTC
Message-ID
<3d6b0edb0908131331l5a3177d1t3d1e1858fc139b2e@mail.gmail.com>
In-Reply-To
<4A840B0F.9060003@alum.mit.edu>
2009/8/13 Michael Haggerty <mhagger@alum.mit.edu>:
> I've been thinking a lot about the problems of tracking upstream changes
> while developing a feature branch.

Isn't this the purpose of pbranch [1] (and I beleive bzr's loom[2] and git's topgit[3])?

Peace, Abderrahim

[1] http://arrenbrecht.ch/mercurial/pbranch/ [2] https://launchpad.net/bzr-loom [3]http://repo.or.cz/w/topgit.git

Previous: Bryan O'Sullivan
Message 10 of 10 in “rebase-with-history -- a technique for rebasing without trashing your repo history”
  1. Michael HaggertyAug 13, 2009
  2. Björn SteinbrinkAug 13, 2009
  3. Michael HaggertyAug 13, 2009
  4. Björn SteinbrinkAug 13, 2009
  5. Michael HaggertyAug 14, 2009
  6. Nanako ShiraishiAug 14, 2009
  7. Björn SteinbrinkAug 15, 2009
  8. Sitaram ChamartyAug 14, 2009
  9. Bryan O'SullivanAug 13, 2009
  10. Abderrahim KitouniAug 13, 2009

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.