git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Jefferis <jefferis@gmail.com>
To: <git@vger.kernel.org>
Subject: Stitching together private svn repo and public git repo
Date: Wed, 02 Jan 2008 19:25:41 +0000	[thread overview]
Message-ID: <C3A195B5.10839%jefferis@gmail.com> (raw)

Short Version: 

Repo B is a completely linear repo that has been tracking public repo A for
some time.  A number of manual merges were done to bring new A releases
into B but there are no connections between the two repos.  (How) can I
stitch B to A to reflect this relationship?  I want to retain B's history
and leave myself with an arrangement in which I can pull from A into B
periodically?  Many thanks for your suggestions, Greg.

--
Long Version:

I have been tracking my modifications of a public project released as tar
balls with my own local svn repository.  My svn repo was completely linear
and I always merged in changes manually each time a new tar ball was
released.  This started to get painful.

Now I want to do better.  I have set up a public git repository ("A") to
track the tar ball releases from the public project.  I have converted my
svn repo with git-svn to a git repo ("B").

My goal is to end up with a (new?) git repo tracking the public repo (A) so
that I can pull in any changes and merge easily. Fine, but I also want to
keep the history that I have imported from my svn repository (B).  So my
question is, can anyone suggest some pointers for how to stitch together A
and B?

Right now I have been trying to pull B into A to splice:

A $ git checkout v1.91
B $ git checkout v1.91-manualmerge
B $ git pull --no-commit -s ours ../A

This looks right when I run gitk, but if I repeat this for a second merge
point then the previous merge seems to disappear from history when I bring
up gitk.

I haven't found any docs/wiki info that has enlightened me yet.  Any
suggestions, wisdom, links etc very much appreciated - I do want to try to
get this right now, so I don't have to rejig everything in the future.  Best
wishes and many thanks,

Greg.

-- 
Gregory Jefferis, PhD                               and:
Research Fellow
Department of Zoology                               St John's College
Downing Street                                      Cambridge
Cambridge, CB2 3EJ                                  CB2 1TP

             reply	other threads:[~2008-01-02 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 19:25 Gregory Jefferis [this message]
2008-01-02 21:40 ` Stitching together private svn repo and public git repo Charles Bailey
2008-01-02 22:13   ` Dmitry Potapov
2008-01-02 22:46     ` Charles Bailey
2008-01-03 14:43       ` Gregory Jefferis
2008-01-03 17:24         ` 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=C3A195B5.10839%jefferis@gmail.com \
    --to=jefferis@gmail.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).