From: Howard Miller <howard@e-learndesign.co.uk>
To: git@vger.kernel.org
Subject: Merging non-git releases of a project
Date: Fri, 9 Oct 2009 22:11:19 +0100 [thread overview]
Message-ID: <26ae428a0910091411i39a03650o51163f794b984524@mail.gmail.com> (raw)
Here's my dilemma.... I've used git extensively to track modifications
made to a reasonably large source tree. I do not have access to the
repository for that project, just a given release. I have now acquired
the latest version of that project and I want to 'merge' (not sure
that's the right word in this case) my changes into the new version.
Then I need to carry on using git for further changes. I think it
should be simple but I can't get my head around the best way to do
this.
Any pointers appreciated!
next reply other threads:[~2009-10-09 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 21:11 Howard Miller [this message]
2009-10-09 21:27 ` Merging non-git releases of a project Avery Pennarun
2009-10-09 21:33 ` Howard Miller
2009-10-09 22:43 ` Avery Pennarun
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=26ae428a0910091411i39a03650o51163f794b984524@mail.gmail.com \
--to=howard@e-learndesign.co.uk \
--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).