git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brent Goodrick <bgoodr@gmail.com>
To: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Trouble testing out a patch on a branch new scratch git.git  repository
Date: Sun, 8 Feb 2009 18:59:34 -0800	[thread overview]
Message-ID: <e38bce640902081859o47462a58s59c120209fabb0@mail.gmail.com> (raw)
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:
> > 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

  reply	other threads:[~2009-02-09  3:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08 20:56 Trouble testing out a patch on a branch new scratch git.git repository Brent Goodrick
2009-02-08 21:46 ` Junio C Hamano
2009-02-09  0:13   ` Brent Goodrick
2009-02-09  1:18     ` Boyd Stephen Smith Jr.
2009-02-09  2:59       ` Brent Goodrick [this message]
2009-02-09  4:58         ` Junio C Hamano
2009-02-09 21:59           ` Brent Goodrick
2009-02-09 22:14             ` Boyd Stephen Smith Jr.
2009-02-10  5:32             ` Sitaram Chamarty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e38bce640902081859o47462a58s59c120209fabb0@mail.gmail.com \
    --to=bgoodr@gmail.com \
    --cc=bss@iguanasuicide.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).