From: David Mansfield <david@cobite.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Ingo Molnar <mingo@elte.hu>,
David Woodhouse <dwmw2@infradead.org>,
git@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: Handling renames.
Date: Thu, 14 Apr 2005 15:21:52 -0400 [thread overview]
Message-ID: <425EC2D0.2090904@cobite.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504141124220.7211@ppc970.osdl.org>
Linus Torvalds wrote:
>
> On Thu, 14 Apr 2005, Ingo Molnar wrote:
>
>>there's no redundancy caused by this method: only renames (which are
>>rare) go through the rename_commit redirection. (to speed up the lookup
>>the rename_commit object could cache the offset of the two names within
>>their tree objects.)
>
>
>
> Some "higher level" thing can add its own rules _on_top_ of git rules. The
> same way we have normal applications having their _own_ rules on top of
> the kernel. You do abstraction in layers, but for this to work, the base
> you build on top of had better be damn solid, and not have any ugly
> special cases.
>
Maybe you (or the group) should standardize on a way to 'extend' the
commit 'object' in terms of:
the layer1 (git) header for commit object is defined as such-and-such
the layer2 (scm or other) header for commit object is defined as
such-and-such
Much the way network protocols stack on top of each other. If a
standard way of stacking is defined, then it could be much cleaner for
future implementors to understand a 'new' stacking protocol, and it will
make the scm-level extensions easier to discuss it terms of their own
'layer'.
David
next prev parent reply other threads:[~2005-04-14 19:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 17:54 Handling renames David Woodhouse
2005-04-14 18:11 ` Linus Torvalds
2005-04-14 19:09 ` David Woodhouse
2005-04-14 18:12 ` Ingo Molnar
2005-04-14 18:32 ` Linus Torvalds
2005-04-14 18:58 ` Ingo Molnar
2005-04-14 19:20 ` David Woodhouse
2005-04-14 19:21 ` David Mansfield [this message]
2005-04-14 18:21 ` H. Peter Anvin
2005-04-14 18:48 ` Linus Torvalds
2005-04-14 18:49 ` H. Peter Anvin
2005-04-14 19:22 ` Zach Welch
2005-04-14 19:40 ` Andrew Timberlake-Newell
2005-04-14 20:42 ` Naming the SCM (was Re: Handling renames.) Steven Cole
2005-04-14 20:53 ` Petr Baudis
2005-04-14 20:58 ` H. Peter Anvin
2005-04-14 21:01 ` Petr Baudis
2005-04-14 23:17 ` Peter Williams
2005-04-14 22:23 ` Handling renames Daniel Barkalow
2005-04-14 22:46 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 13:37 linux
2005-04-15 13:53 ` David Woodhouse
2005-10-21 23:40 git-rev-list: add "--dense" flag Linus Torvalds
2005-10-22 0:37 ` Petr Baudis
2005-10-22 0:47 ` Handling renames Petr Baudis
2005-10-22 1:28 ` Linus Torvalds
2005-10-22 1:51 ` Petr Baudis
2005-10-22 2:10 ` Junio C Hamano
2005-10-22 2:49 ` Petr Baudis
2005-10-22 3:23 ` Linus Torvalds
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=425EC2D0.2090904@cobite.com \
--to=david@cobite.com \
--cc=James.Bottomley@SteelEye.com \
--cc=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).