git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Workflow: split repository?

From
JWJan Wielemaker <wielemak@science.uva.nl>
Date
Oct 12, 2007, 14:57 UTC
Message-ID
<200710121657.01256.wielemak@science.uva.nl>
In-Reply-To
<20071012143043.GD7865@efreet.light.src>
Hi Jan,
On Friday 12 October 2007 16:30, Jan Hudec wrote:
Show 5 quoted lines
> 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.
Show 10 quoted lines
> > 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
Previous: Jan Hudec
Message 3 of 3 in “Workflow: split repository?”
  1. Jan WielemakerOct 12, 2007
  2. Jan HudecOct 12, 2007
  3. Jan WielemakerOct 12, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.