From: "Mikhail T." <mi+thun@aldan.algebra.com>
To: git@vger.kernel.org
Subject: How to fork a file (git cp ?)
Date: Wed, 04 May 2011 13:56:29 -0400 [thread overview]
Message-ID: <4DC1934D.6070608@aldan.algebra.com> (raw)
I need to add a new thing to our project. The thing will be similar to what
already exists. I'd like to "derive" the new files from the existing ones --
without altering them and by preserving the change-history.
This is not a separate branch -- the "forked" files will co-exist. I'd call this
git-cp (analogous to git-mv), but it does not exist...
Any ideas? Thanks!
-mi
next reply other threads:[~2011-05-04 18:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 17:56 Mikhail T. [this message]
2011-05-04 18:16 ` How to fork a file (git cp ?) Johannes Sixt
2011-05-04 18:22 ` Johannes Sixt
2011-05-04 19:05 ` Stephen Bash
2011-05-04 19:17 ` Mikhail T.
2011-05-04 20:36 ` Øyvind A. Holm
2011-05-04 21:02 ` Junio C Hamano
2011-05-05 1:58 ` Mikhail T.
2011-05-05 2:14 ` Junio C Hamano
2011-05-05 18:02 ` Piotr Krukowiecki
2011-05-05 18:50 ` Junio C Hamano
2011-05-05 19:27 ` Piotr Krukowiecki
2011-05-05 19:31 ` Mikhail T.
2011-05-05 20:01 ` Jeff King
2011-05-05 20:01 ` Piotr Krukowiecki
2011-05-05 20:06 ` Piotr Krukowiecki
2011-05-05 20:07 ` Jeff King
2011-05-08 19:40 ` Pete Harlan
2011-05-08 20:03 ` 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=4DC1934D.6070608@aldan.algebra.com \
--to=mi+thun@aldan.algebra.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 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).