From: Ping Yin <pkufranky@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git mailing list <git@vger.kernel.org>
Subject: Re: How to create a new commit with the content of some commit?
Date: Wed, 13 May 2009 00:43:33 +0800 [thread overview]
Message-ID: <46dff0320905120943j303ef104ve7bad25f1874007f@mail.gmail.com> (raw)
In-Reply-To: <20090512160749.GA29566@coredump.intra.peff.net>
On Wed, May 13, 2009 at 12:07 AM, Jeff King <peff@peff.net> wrote:
> On Tue, May 12, 2009 at 10:35:30PM +0800, Ping Yin wrote:
>
>> a----b
>> \----c
>>
>> Given the graph above, I want to create a commit b1 on top of c, where
>> b1 and b have the same content. i.e.
>>
>> a----b
>> \----c----b1 ( content(b) == content(b1) )
>>
>> If there are no untracked files in the working directory, i can do
>>
>> git checkout b
>> git reset c
>> git add .
>> git commit -m "the copy of b"
>>
>> Is there any simpler way? And if there are untracked files in the
>> working directory, how to do it?
>
> You can just munge the index directly, and skip the working tree
> entirely:
>
> rm .git/index
> git read-tree b
> git commit -m 'the copy of b'
In a non-conflict status, "git read-tree b" will update the index to
full match the tree of b, so "rm .git/index" is unnecessary, right?
> You can also do it without even touching the index by using the commit
> plumbing:
>
> echo 'copy of b' >message
> tree=`git rev-parse b^{tree}`
> commit=`git commit-tree $tree -p c <message`
> git update-ref c $commit
Nice solution. Thank you and thank so powerful git!
Maybe a -c option can be added to git-commit-tree?
next prev parent reply other threads:[~2009-05-12 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 14:35 How to create a new commit with the content of some commit? Ping Yin
2009-05-12 15:47 ` Ping Yin
2009-05-12 16:04 ` Tomas Carnecky
2009-05-13 14:36 ` Sitaram Chamarty
2009-05-12 15:59 ` Junio C Hamano
2009-05-12 16:38 ` Ping Yin
2009-05-12 16:07 ` Jeff King
2009-05-12 16:43 ` Ping Yin [this message]
2009-05-12 16:51 ` Jeff King
2009-05-12 16:59 ` Ping Yin
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=46dff0320905120943j303ef104ve7bad25f1874007f@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).