git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Wielemaker <wielemak@science.uva.nl>
To: Jan Hudec <bulb@ucw.cz>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Workflow: split repository?
Date: Fri, 12 Oct 2007 16:57:01 +0200	[thread overview]
Message-ID: <200710121657.01256.wielemak@science.uva.nl> (raw)
In-Reply-To: <20071012143043.GD7865@efreet.light.src>

Hi Jan,

On Friday 12 October 2007 16:30, Jan Hudec wrote:
> On Fri, Oct 12, 2007 at 14:21:39 +0200, Jan Wielemaker wrote:
> > Does this make sense?
>
> It might make more sense to convert bit by bit, to separate git
> repositories. Would save you some git-filter-branch work.

> > Is the only way to create a GIT repositiory right away from a subset of
> > the CVS for which we want to preserve the history?
>
> No, it's not. It will save you work if you can do as much splitting as
> possible during the conversion, ie. convert the bits you know will be
> separate separately (and combine them using submodules as appropriate).
>
> But if you have bits that will take a lot of work to factor out, you can
> convert to git, make the other code ready to use a submodule and than use
> git-filter-branch to extract the right bits of history for the submodule.

Thanks!  git-filter-branch looks a bit overwhelming, but I think I can
manage :-)  I'll do the simple things in separate conversions.

	Cheers --- Jan

      reply	other threads:[~2007-10-12 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 12:21 Workflow: split repository? Jan Wielemaker
2007-10-12 14:30 ` Jan Hudec
2007-10-12 14:57   ` Jan Wielemaker [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=200710121657.01256.wielemak@science.uva.nl \
    --to=wielemak@science.uva.nl \
    --cc=bulb@ucw.cz \
    --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).