From: Ealdwulf Wuffinga <ealdwulf@googlemail.com>
To: Sal Mangano <smangano@into-technology.com>
Cc: git@vger.kernel.org
Subject: Re: Supressing sorting of trees
Date: Tue, 13 Oct 2009 21:49:22 +0100 [thread overview]
Message-ID: <efe2b6d70910131349n4cab61d0h9a9c8099830095f9@mail.gmail.com> (raw)
In-Reply-To: <loom.20091012T182258-9@post.gmane.org>
On Mon, Oct 12, 2009 at 5:51 PM, Sal Mangano
<smangano@into-technology.com> wrote:
> 1) I can write by repository from scratch.
> 2) I can use Git unchanged but preserve order by storing some information in
> each sub tree (e.g. an extra blob) which retains the real order. I can also
> store this information once for the whole "chunks" of the repository.
> 3) I can change Git to suite my needs understanding that it is not Git
> anymore.
>
> For me, (1) makes no sense at this time. I started with the hope that (2)
> would work but realized it is very awkward and will cause performance problems
> because it means most updates where ordering matters will have to update the
> Git trees and my private ordering blob(s). So, after a quick look at the
> source code it seemed like hacking Git into what I wanted was easier than 1
> or 2.
You could add a prefix to the names so you get the order you want. Eg:
a-foo
b-bar
c-baz
If you need to move foo to between bar and baz, you just rename it to
ba-foo, etc.
Ealdwulf
prev parent reply other threads:[~2009-10-13 20:58 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
2009-10-13 20:49 ` Ealdwulf Wuffinga [this message]
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=efe2b6d70910131349n4cab61d0h9a9c8099830095f9@mail.gmail.com \
--to=ealdwulf@googlemail.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).