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
Brent Goodrick <bgoodr@gmail.com>
Date
Feb 9, 2009, 02:59 UTC
Message-ID
<e38bce640902081859o47462a58s59c120209fabb0@mail.gmail.com>
In-Reply-To
<200902081918.35665.bss@iguanasuicide.net>

On Sun, Feb 8, 2009 at 5:18 PM, Boyd Stephen Smith Jr. <bss@iguanasuicide.net> wrote:

Show 7 quoted lines
> > What do you mean by "reorder, squash" mean here? Is that something
> > that is done as a part of the -i option to git rebase?
>
> Reordering and squashing can be done via rebase -i, but it's basically just
> the practice of "prettying" your changes.
> http://magazine.redhat.com/2008/05/02/shipping-quality-code-with-git/ has more
> prose on the subject.

Thanks Boyd. I made the mistake of using git revert HEAD thinking it would just delete that last revision, but it instead added a new revision that acted as if it just reversed the changes.

What I really want to do is simply replace the last two commits on the branch with one commit, so that when I make my patch it will be just the full set of changes and not a lot of noise. Is there a way to do that? (note: I did try the git merge --squash command but it just showed me the usage, as I was on my bg/no-progress branch). Note that I know that I would not be able to do this once some of my changes had merged upstream.

Thanks, bgoodr

Previous: Boyd Stephen Smith Jr.Next: Junio C Hamano
Message 5 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.