From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: eschvoca <eschvoca@gmail.com>
Cc: kusmabite@gmail.com, git@vger.kernel.org
Subject: Re: git rebase -i <first_commit_in_repository>
Date: Mon, 26 Oct 2009 21:28:25 +0100 [thread overview]
Message-ID: <4AE60669.9080402@dirk.my1.cc> (raw)
In-Reply-To: <2b05065b0910261108g4a8448c8x295606a8d33612f5@mail.gmail.com>
Am 26.10.2009 19:08 schrieb eschvoca:
> 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.
Hi,
probably my approach could help you in the future: When I create a new
repo (git init) I firstly create an initial commit with nothing else
than an initial commit, i.e.:
$ git init
$ echo "initial" > initial.commit
$ git add initial.commit
$ git commit -m "Initial commit"
and then secondly
$ git add .
$ git commit -m "*REAL* initial commit"
Afterwards I have a repo with an initial commit that only contains one
file (initial.commit) and the "real" initial commits thereafter. Maybe
that's a solution for you.
Cheers,
Dirk
next prev parent reply other threads:[~2009-10-26 20:31 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 [this message]
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
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=4AE60669.9080402@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=eschvoca@gmail.com \
--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).