From: Avery Pennarun <apenwarr@gmail.com>
To: Howard Miller <howard@e-learndesign.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Merging non-git releases of a project
Date: Fri, 9 Oct 2009 18:43:50 -0400 [thread overview]
Message-ID: <32541b130910091543x19b3b46an109f90be5c5bfaa2@mail.gmail.com> (raw)
In-Reply-To: <26ae428a0910091433v2c959a70g9bfc6c54382f370d@mail.gmail.com>
On Fri, Oct 9, 2009 at 5:33 PM, Howard Miller
<howard@e-learndesign.co.uk> wrote:
> I'm missing the point here though. Where/when do I actually add the
> new pristine code? If I checkout, as you suggest, my initial commit I
> just have (say) v1.0 of the vendor's code. I can't just copy (say)
> version 1.2 on top as the files probably won't match one-one.
>
> Sorry - I'm probably completely failing to understand.
Try this:
cd mygitproject
git rm -rf .
cp -a /tmp/wherever/vendor-1.2/. .
git add .
git commit
Don't worry, git won't double-store files that are identical between
the old 1.0 and new 1.2 versions.
Avery
next prev parent reply other threads:[~2009-10-09 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 21:11 Merging non-git releases of a project Howard Miller
2009-10-09 21:27 ` Avery Pennarun
2009-10-09 21:33 ` Howard Miller
2009-10-09 22:43 ` Avery Pennarun [this message]
2009-10-10 8:47 ` Peter Baumann
2009-10-10 9:00 ` Björn Steinbrink
2009-10-10 10:04 ` Peter Baumann
2009-10-10 8:58 ` Howard Miller
2009-10-11 15:32 ` Avery Pennarun
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=32541b130910091543x19b3b46an109f90be5c5bfaa2@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=howard@e-learndesign.co.uk \
/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).