From: Peter Karlsson <peter@softwolves.pp.se>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Lars Hjemli <hjemli@gmail.com>,
Benoit SIGOURE <tsuna@lrde.epita.fr>,
git@vger.kernel.org
Subject: Re: Recording merges after repo conversion
Date: Wed, 31 Oct 2007 10:50:02 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.62.0710311048450.13264@perkele.intern.softwolves.pp.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0710310227340.4362@racer.site>
Johannes Schindelin:
> Why should it? This would contradict the whole "a commit sha1 hashes the
> commit, and by inference the _whole_ history" principle.
Does it? Why can't the grafts file itself be committed to the repository and
live in the history?
Well, yeah, the SHA1 hashing is one of Git's main strengths, but it also
opens up some weaknesses.
--
\\// Peter - http://www.softwolves.pp.se/
next prev parent reply other threads:[~2007-10-31 9:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 7:09 Recording merges after repo conversion Peter Karlsson
2007-10-09 7:19 ` Benoit SIGOURE
2007-10-30 13:34 ` Peter Karlsson
2007-10-30 14:29 ` Lars Hjemli
2007-10-30 21:06 ` Peter Karlsson
2007-10-30 21:46 ` Lars Hjemli
2007-10-31 2:28 ` Johannes Schindelin
2007-10-31 9:50 ` Peter Karlsson [this message]
2007-10-31 11:01 ` Johannes Schindelin
2007-10-31 12:07 ` Peter Karlsson
2007-10-31 12:32 ` Johannes Schindelin
2007-10-31 12:43 ` Johan Herland
2007-10-31 13:43 ` Johannes Schindelin
2007-10-31 14:37 ` Johan Herland
2007-10-31 15:03 ` Johannes Schindelin
2007-10-31 15:21 ` Johan Herland
2007-10-31 15:57 ` Johannes Schindelin
2007-10-31 16:43 ` Linus Torvalds
2007-10-31 17:08 ` Johan Herland
2007-10-30 15:05 ` Johannes Schindelin
2007-10-31 12:17 ` Peter Karlsson
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=Pine.LNX.4.62.0710311048450.13264@perkele.intern.softwolves.pp.se \
--to=peter@softwolves.pp.se \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=tsuna@lrde.epita.fr \
/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).