git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Salvatore Mangano <smangano@into-technology.com>
Cc: git@vger.kernel.org
Subject: Re: Supressing sorting of trees
Date: Mon, 12 Oct 2009 22:24:16 +0200	[thread overview]
Message-ID: <46a038f90910121324s34c29133t7ba4558771bf404f@mail.gmail.com> (raw)
In-Reply-To: <DF65B4B0-62B1-4469-99E1-3305434F9D59@into-technology.com>

On Mon, Oct 12, 2009 at 10:02 PM, Salvatore Mangano
<smangano@into-technology.com> wrote:
> point to specific code

Shaun pointed out some very core code. And it is just a core concept.
Just read up on the core organizing concept that is the "tree". Git
relies on the layout of the tree being strictly deterministic.

It is a prevalent assumption in the whole codebase.

Yes you can change it, but assume you will have to audit/rewrite 80%
of the core code.

Want "proof"? Go change it, then try "make  test", or reimport a large
repository try to use the git commands over it. We'll relax and watch
the fireworks :-)



m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

  reply	other threads:[~2009-10-12 20:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 13:27 Supressing sorting of trees Sal Mangano
2009-10-12 14:20 ` Shawn O. Pearce
2009-10-12 15:43   ` Sal Mangano
2009-10-12 16:05     ` Johannes Schindelin
2009-10-12 16:51       ` Sal Mangano
2009-10-12 19:36         ` Martin Langhoff
2009-10-12 20:02           ` Salvatore Mangano
2009-10-12 20:24             ` Martin Langhoff [this message]
2009-10-13 20:49         ` Ealdwulf Wuffinga

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=46a038f90910121324s34c29133t7ba4558771bf404f@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=smangano@into-technology.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).