git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Hühn" <newsgroups@thomas-huehn.de>
To: git@vger.kernel.org
Subject: incorporating the past
Date: Mon, 09 Apr 2007 20:14:17 +0200	[thread overview]
Message-ID: <87d52d1kli.fsf@mid.thomas-huehn.de> (raw)

Hi

I have looked through some git tutorials and the manual, and what is
interesting me most right now is, how do I handle a situation like this
with git? It's purely speculative, I don't have such a situation in
reality, so my description might be a bit murky...

I'll try to make an extremely simple example, just one file, no
branching etc.

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.

Can I just do another git init for 0.1, commit the changes up to 1.0 and
merge those two histories? Don't I need a common ancestor for both or
something like that?

Or can I do the same, only up to 0.9 instead of 1.0, and then "sew
together" those histories?

Is there some kind of "add-past", where the changed contents in the
working directory are prepended, not appended to the history? So that I
could "prepend" 0.9, then 0.8 and so on until 0.1?

I guess, I just don't have a clear grasp of what "history" and "branch"
and so on mean.

Thomas

             reply	other threads:[~2007-04-09 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 18:14 Thomas Hühn [this message]
2007-04-09 18:32 ` incorporating the past Shawn O. Pearce
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=87d52d1kli.fsf@mid.thomas-huehn.de \
    --to=newsgroups@thomas-huehn.de \
    --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).