All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
Subject: Re: reverting initial commit
Date: Wed, 25 Mar 2009 20:45:19 +0100	[thread overview]
Message-ID: <gqe1kf$pg1$1@ger.gmane.org> (raw)
In-Reply-To: 8c9a060903251133x33749041oc2a5152097da0ae8@mail.gmail.com

On Wednesday 25 March 2009 19:33, Jacob Helwig wrote:
> On Wed, Mar 25, 2009 at 11:26, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> That's not even an revert.  Can't you simply amend it away?
>>
>>        $ git rm not-this-file
>>        $ git commit --amend
> 
> This is obviously the easier way.  (Or a rebase --interactive)

Actually, rebase --interactive cannot be used to amend the first commit.
This is something that has hit me a couple of times when I realised, after
the second or third commit, that I needed to fix the first one. I found
the fastest way in this case to be to just format-patch all but the first
commit, reset --hard to the first commit, amend, and git am what I format-
patched.

I wish there was a way to tell rebase -i to go back to the first commit,
inclusive, but the two or three times I've tried hacking at it I never
managed to come to anything useful 8-/

-- 
Giuseppe "Oblomov" Bilotta

  reply	other threads:[~2009-03-25 19:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 18:12 reverting initial commit Pascal Obry
2009-03-25 18:20 ` Jacob Helwig
2009-03-25 18:26 ` Junio C Hamano
2009-03-25 18:33   ` Jacob Helwig
2009-03-25 19:45     ` Giuseppe Bilotta [this message]
2009-03-25 20:40       ` Sverre Rabbelier
2009-03-25 21:22         ` Giuseppe Bilotta
2009-03-25 21:06       ` Eric Raible
2009-03-25 18:36   ` Pascal Obry
2009-03-25 18:40     ` 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='gqe1kf$pg1$1@ger.gmane.org' \
    --to=giuseppe.bilotta@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.