From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Thomas Hühn" <newsgroups@thomas-huehn.de>
Cc: git@vger.kernel.org
Subject: Re: incorporating the past
Date: Mon, 9 Apr 2007 14:32:10 -0400 [thread overview]
Message-ID: <20070409183210.GX5436@spearce.org> (raw)
In-Reply-To: <87d52d1kli.fsf@mid.thomas-huehn.de>
Thomas H??hn <newsgroups@thomas-huehn.de> wrote:
> I have a file under version control, that I got at the point of file
> version 1.0. I start committing changes:
>
> o--o--o--o--o--o--o
> ^ ^
> git init, current,
> version 1.0 version 1.6
>
> Then I get the history up to my version 1.0 from somewhere else (former
> maintainer, whatever). In the form of plain text files, one for each
> version; say, versions 0.1 thru 0.9. I want to incorporate this past
> into my tree.
>
> Or can I do the same, only up to 0.9 instead of 1.0, and then "sew
> together" those histories?
Yes. Look at the `grafts' file. You can create a new repository
of the 0.9..1.0 history, then graft that repository as a new parent
of the 1.0 commit. This lets you join in the old history behind
the existing history. The Linux kernel folks have done this for
the kernel repository.
--
Shawn.
next prev parent reply other threads:[~2007-04-09 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 18:14 incorporating the past Thomas Hühn
2007-04-09 18:32 ` Shawn O. Pearce [this message]
2007-04-09 19:59 ` 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=20070409183210.GX5436@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=newsgroups@thomas-huehn.de \
/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).