Re: Supressing sorting of trees
- From
- Ealdwulf Wuffinga <ealdwulf@googlemail.com>
- Date
- Oct 13, 2009, 20:49 UTC
- Message-ID
- <efe2b6d70910131349n4cab61d0h9a9c8099830095f9@mail.gmail.com>
- 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:
Show 13 quoted lines
> 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