git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kris Shannon <kris.shannon.kernel@gmail.com>
To: GIT Mailing List <git@vger.kernel.org>
Subject: RT[0/3]: Some related random thoughts
Date: Thu, 28 Apr 2005 22:59:44 +1000	[thread overview]
Message-ID: <5d4799ae0504280559109cd00e@mail.gmail.com> (raw)

I've had a number of thoughts about the "supposed" missing SCM features of git.

1) Alternate Encodings (including on-disk delta compression)
    If the default objects filename doesn't exist, we can try for
other alternative
    encodings e.g. 00/a29c403e751c2a2a61eb24fa2249c8956d1c80.xdelta which
    can specify the object content as a delta or other ingenious idea...

2) Rename/Code-movement Tracking (file and/or function)
    Additional object type tag(s) "rename" which references a changeset
    and lists the movement metadata

3) SHA1 backwards reference cache
    Allows quickly finding all commits which reference a given tree root,
    all/the "rename" for a given commit, all xdeltas which use this blob.

There a quite a few important issues with all 3 of these ideas so I
thought I would
elaborate each in separate emails... (coming soon :)

-- 
Kris Shannon <kris.shannon.kernel@gmail.com>

             reply	other threads:[~2005-04-28 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 12:59 Kris Shannon [this message]
2005-04-28 13:34 ` RT[2/3]: Rename/Code-movement Tracking Kris Shannon
2005-04-28 13:47 ` RT[1/3]: Alternate Encodings (esp. Delta Compression) Kris Shannon
2005-04-28 13:54 ` RT[3/3]: Reverse lookup of SHA1 references Kris Shannon
     [not found]   ` <42717714.50601@dwheeler.com>
2005-04-29  0:11     ` Kris Shannon

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=5d4799ae0504280559109cd00e@mail.gmail.com \
    --to=kris.shannon.kernel@gmail.com \
    --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).