From: Junio C Hamano <gitster@pobox.com>
To: Yuval Adam <yuv.adm@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Maintaining historical data in a git repo
Date: Fri, 30 Mar 2012 09:52:04 -0700 [thread overview]
Message-ID: <7vehsam3pn.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CA+P+rLcWT0SZQjW2LtFXXCDRwjMp8daJ2hVup=7cnsRGbKw7xw@mail.gmail.com> (Yuval Adam's message of "Fri, 30 Mar 2012 18:55:51 +0300")
Yuval Adam <yuv.adm@gmail.com> writes:
> Is this something that is definitively complicated with git?
That's not really "is it complicated with git" question, I would have to
say. Any version control system you would build history starting from one
point going _forward_, never inserting past event as you dig back.
Surely, you could fake it by rewriting history, but I do not think SCM is
particularly geared towards such a use case *while* investigating the
history of the law and recording your findings.
I do agree that once such a discovered history is *complete*, it would be
nice to record it in a SCM with a powerful history digging capability in
chronological order, though.
next prev parent reply other threads:[~2012-03-30 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 13:34 Maintaining historical data in a git repo Yuval Adam
2012-03-30 15:10 ` Seth Robertson
2012-03-30 15:55 ` Yuval Adam
2012-03-30 16:18 ` Seth Robertson
2012-03-30 16:32 ` Jakub Narebski
2012-03-30 16:52 ` Junio C Hamano [this message]
2012-03-30 20:39 ` Yuval Adam
2012-03-30 22:29 ` david
2012-03-31 1:04 ` Mark Lodato
2012-04-01 4:14 ` Holding, Lawrence
2012-04-02 11:38 ` Ævar Arnfjörð Bjarmason
2012-04-03 19:45 ` Maintaining historical outlines Markus Elfring
2012-04-03 9:25 ` Maintaining historical data in a git repo Andreas Stricker
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=7vehsam3pn.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=yuv.adm@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).