git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Roger Garvin <yoyodyn@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Adding History
Date: Thu, 19 Mar 2009 10:47:32 -0700	[thread overview]
Message-ID: <20090319174732.GS23521@spearce.org> (raw)
In-Reply-To: <loom.20090319T173541-173@post.gmane.org>

Roger Garvin <yoyodyn@gmail.com> wrote:
> Is there a way to add history to a repository?
> We have just started using git, where before we had nothing but backup
> directories all over the place.  We created the git repository using our
> existing source directory.  Is there a way to now go and add some of the backup
> source directories to the history?  Or would this break all the SHA1 of the
> current objects?

Right, you need to change the SHA-1 of all of the commits in order
to insert history in the past.

> I am not sure it would be worth it at this point.  But we are
> still pretty early in our use of git so now would be the easiest time.  

You have two options:

- Use git-filter-branch now to rewrite your commits with the
history added.  Its a one-time pain that you need to go through to
discard all of your current objects, and move to the new ones that
have the history.

- Keep the current objects, but if you need the history, add it
to the local repository by editing the grafts file.  This is how
the Linux kernel team can insert history that predates Git, if
they absolutely must have it.

It depends on how often you need to look at that history.  If its
"almost never", I would probably go with the graft.  If its "often",
I would consider the filter-branch now.

-- 
Shawn.

  reply	other threads:[~2009-03-19 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 17:38 Adding History Roger Garvin
2009-03-19 17:47 ` Shawn O. Pearce [this message]
2009-03-20  5:25   ` John Tapsell

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=20090319174732.GS23521@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=yoyodyn@gmail.com \
    /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).