From: eschvoca <eschvoca@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: kusmabite@gmail.com, git@vger.kernel.org
Subject: Re: git rebase -i <first_commit_in_repository>
Date: Mon, 26 Oct 2009 20:27:13 -0400 [thread overview]
Message-ID: <2b05065b0910261727g75e4330fn23ed6c633114e689@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0910262210480.4985@pacific.mpi-cbg.de>
Hi,
On Mon, Oct 26, 2009 at 5:11 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Mon, 26 Oct 2009, eschvoca wrote:
>
>> On Mon, Oct 26, 2009 at 1:25 PM, Erik Faye-Lund
>> <kusmabite@googlemail.com> wrote:
>> > On Mon, Oct 26, 2009 at 6:14 PM, eschvoca <eschvoca@gmail.com> wrote:
>> >> Hi,
>> >>
>> >> Is there a way to rewrite history, including the first commit. It
>> >> seems that the first commit can not be modified with a rebase.
>> >
>> > This question is answered in the FAQ:
>> > http://git.or.cz/gitwiki/GitFaq#HowdoIedittherootcommit.3F
>>
>> Thanks Eric. Hopefully someone will enhance rebase to handle the root
>> commit.
>
> If you cannot do it yourself, you can always offer to bribe^Wpay somebody
> to do it for you.
>
> Ciao,
> Dscho
>
I can do the workaround myself but not the production ready patch.
Right now the only bribe I can offer is that it might be less work
writing the patch than supporting this corner case with answering
questions and writing a FAQ entry about it. It also would make the
awesome rebase -i even awesomer :) I know, a disappointing bribe but
from a thankful user.
Thanks
prev parent reply other threads:[~2009-10-27 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 17:14 git rebase -i <first_commit_in_repository> eschvoca
2009-10-26 17:24 ` Mike Hommey
2009-10-26 17:25 ` Erik Faye-Lund
2009-10-26 18:08 ` eschvoca
2009-10-26 20:28 ` Dirk Süsserott
2009-10-26 20:47 ` Allan Caffee
2009-10-28 19:24 ` Dirk Süsserott
2009-10-26 21:11 ` Johannes Schindelin
2009-10-27 0:27 ` eschvoca [this message]
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=2b05065b0910261727g75e4330fn23ed6c633114e689@mail.gmail.com \
--to=eschvoca@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.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).