git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniele Segato <daniele.bilug@gmail.com>
To: Howard Miller <howard@e-learndesign.co.uk>
Cc: Jacob Helwig <jacob.helwig@gmail.com>,
	Bill Lear <rael@zopyra.com>,
	git@vger.kernel.org
Subject: Re: Any way to "flatten" a series of changes in git
Date: Mon, 26 Oct 2009 14:42:23 +0100	[thread overview]
Message-ID: <9accb4400910260642w360e2879vd3b1b1efc3613a13@mail.gmail.com> (raw)
In-Reply-To: <26ae428a0910221358r47434b4uf7ec71f9376b9f75@mail.gmail.com>

On Thu, Oct 22, 2009 at 9:58 PM, Howard Miller
<howard@e-learndesign.co.uk> wrote:
>> git merge --squash topic

>> rebase --interactive it excellent for cleaning up history, especially [...]

> Brilliant, thanks everybody!! I'll go and back up my database and have
> a play with these options.


I don't think you need it.
when you rebase or squash git don't throw away your commits

when I do things like that I usually create a new branch to do my tests

if I'm happy with the result I can do

git checkout myRealBranch
git reset --hard myTestBranch
# do the push/svn dcommit/whatever

if I'm not happy I can start all over again just doing:

git checkout MyTestBranch
git reset --hard myRealBranch

regards,
Daniele

  reply	other threads:[~2009-10-26 13:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 20:03 Any way to "flatten" a series of changes in git Howard Miller
2009-10-22 20:30 ` Bill Lear
2009-10-22 20:44   ` Bill Lear
2009-10-22 20:51     ` Jacob Helwig
2009-10-22 20:58       ` Howard Miller
2009-10-26 13:42         ` Daniele Segato [this message]
2009-10-22 20:59 ` Jakub Narebski
2009-10-22 21:11   ` Howard Miller
2009-10-22 21:24     ` Howard Miller
2009-10-22 21:57     ` Jakub Narebski
2009-10-23  5:36       ` Howard Miller
2009-10-23  5:40         ` Howard Miller
2009-10-23  5:48     ` Johannes Sixt
2009-10-23  6:16       ` Junio C Hamano

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=9accb4400910260642w360e2879vd3b1b1efc3613a13@mail.gmail.com \
    --to=daniele.bilug@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=howard@e-learndesign.co.uk \
    --cc=jacob.helwig@gmail.com \
    --cc=rael@zopyra.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).