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

Re: cookbook question

From
Charles Bailey <charles@hashpling.org>
Date
Feb 28, 2008, 23:20 UTC
Message-ID
<20080228232031.GB31479@hashpling.org>
In-Reply-To
<47C73ED3.6000704@krose.org>
On Thu, Feb 28, 2008 at 06:08:03PM -0500, Kyle Rose wrote:
Show 5 quoted lines
> The rebase just avoids unnecessary merge records.  What I really want is my 
> changes placed on top of whatever the common head is at any one time, which 
> by design means I would use rebase.  Aside from the cleanliness of the 
> history, I'm not sure there is a real reason to do this.  But I like things 
> clean. ;-)

rebase should just reorder the patches in the simple cases, so it should do what you want. Either you've found a bug in rebase or you're doing something unconventional.

Previous: Kyle Rose
Message 4 of 4 in “cookbook question”
  1. Kyle RoseFeb 28, 2008
  2. Charles BaileyFeb 28, 2008
  3. Kyle RoseFeb 28, 2008
  4. Charles BaileyFeb 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.