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

Re: Joining historical repository using grafts or replace

From
W. Trevor King <wking@tremily.us>
Date
Oct 30, 2014, 15:44 UTC
Message-ID
<20141030154426.GU15443@odin.tremily.us>
In-Reply-To
<CA+POfmvCiNBF=P-OvQBTROVhaLtOdgNTDgPNyS=97bupSGk=4g@mail.gmail.com>
On Thu, Oct 30, 2014 at 06:39:56PM +0300, Dmitry Oksenchuk wrote:
Show 10 quoted lines
> We're in the middle of conversion of a large CVS repository (20
> years, 70K commits, 1K branches, 10K tags) to Git and considering
> two separate Git repositories: "historical" with CVS history and
> "working" created without history from heads of active branches (10
> active branches). This allows us to have small fast "working"
> repository for developers who don't want to have full history
> locally and ability to rewrite history in "historical" repository
> (for example, to add parents to merge commits or to fix conversion
> mistakes) without affecting commit hashes in "working" repository
> (the hashes can be stored in bug tracker or in the code).

A number of projects have done something like this (e.g. Linux). Modern Gits have good support for shallow repositories though, so I'd just make one full repository and leave it to developers to decide how deep they want their local copy to be.

Cheers, Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
Previous: Dmitry OksenchukNext: Dmitry Oksenchuk
Message 2 of 8 in “Joining historical repository using grafts or replace”
  1. Dmitry OksenchukOct 30, 2014
  2. W. Trevor KingOct 30, 2014
  3. Dmitry OksenchukOct 30, 2014
  4. Christian CouderOct 30, 2014
  5. Dmitry OksenchukOct 30, 2014
  6. Christian CouderOct 31, 2014
  7. Dmitry OksenchukOct 31, 2014
  8. Christian CouderNov 1, 2014

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.