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

Re: Trouble testing out a patch on a branch new scratch git.git repository

From
Boyd Stephen Smith Jr. <bss@iguanasuicide.net>
Date
Feb 9, 2009, 22:14 UTC
Message-ID
<200902091615.24958.bss@iguanasuicide.net>
In-Reply-To
<e38bce640902091359j3f306839h9aeb699e18e420ab@mail.gmail.com>
On Monday 09 February 2009 15:59:40 Brent Goodrick wrote:
Show 16 quoted lines
> To explain what I mean: Yesterday, I had this configuration on my
> bg/no-progress branch:
>
>              A---B---C---D (bg/no-progress)
>             /
> ----1-----2----3----4 (master)
>
> B C and D commits are noisy,
> fix-the-white-space-and-conform-to-coding-guidelines type commits. I
> want to collapse A through D into one commit called E on that branch
> so that I can run git format-patch -M on the result and provide a nice
> patch email. I would end up with:
>
>              E (bg/no-progress)
>             /
> ----1-----2----3----4 (master)

Here's my way to do that: git rebase -i $(git merge-base master bg/noprogress) bg/no-progress # Editor opens # Change "pick" -> "squash" for commits B, C, and D. # rebase runs # Maybe resolve conflicts

If you are willing to have:
             E (bg/no-progress)
            /
--1--2--3--4 (master)

at the end, it's a little bit simpler: git rebase -i master bg/no-progress # All the rest the same.

-- 
Boyd Stephen Smith Jr.           	 ,= ,-_-. =.
bss@iguanasuicide.net            	((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy 	 `-'(. .)`-'
http://iguanasuicide.net/        	     \_/
Previous: Brent GoodrickNext: Sitaram Chamarty
Message 8 of 9 in “Trouble testing out a patch on a branch new scratch git.git repository”
  1. Brent GoodrickFeb 8, 2009
  2. Junio C HamanoFeb 8, 2009
  3. Brent GoodrickFeb 9, 2009
  4. Boyd Stephen Smith Jr.Feb 9, 2009
  5. Brent GoodrickFeb 9, 2009
  6. Junio C HamanoFeb 9, 2009
  7. Brent GoodrickFeb 9, 2009
  8. Boyd Stephen Smith Jr.Feb 9, 2009
  9. Sitaram ChamartyFeb 10, 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.