From: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
To: Emily Ren <lingyan.ren@gmail.com>
Cc: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>, git@vger.kernel.org
Subject: Re: How can I merge some files rather than all files modified on one branch to my branch?
Date: Wed, 4 Mar 2009 01:10:40 +0100 [thread overview]
Message-ID: <20090304001040.GA13040@vidovic> (raw)
In-Reply-To: <856bfe0e0903021956l549e41d2l97d7e0997067c133@mail.gmail.com>
On Tue, Mar 03, 2009 at 11:56:03AM +0800, Emily Ren wrote:
> Boyd,
> How to rewrite the history of the branch ?
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#cleaning-up-history
--
Nicolas Sebrecht
prev parent reply other threads:[~2009-03-04 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 9:19 How can I merge some files rather than all files modified on one branch to my branch? Emily Ren
2009-03-02 10:04 ` Junio C Hamano
2009-03-03 3:10 ` Boyd Stephen Smith Jr.
2009-03-03 3:56 ` Emily Ren
2009-03-04 0:10 ` Nicolas Sebrecht [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=20090304001040.GA13040@vidovic \
--to=nicolas.s-dev@laposte.net \
--cc=bss@iguanasuicide.net \
--cc=git@vger.kernel.org \
--cc=lingyan.ren@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).