From: Martin Langhoff <martin.langhoff@gmail.com>
To: Sal Mangano <smangano@into-technology.com>
Cc: git@vger.kernel.org
Subject: Re: Supressing sorting of trees
Date: Mon, 12 Oct 2009 21:36:59 +0200 [thread overview]
Message-ID: <46a038f90910121236x6bbe258bwa3bc3fdcc54de524@mail.gmail.com> (raw)
In-Reply-To: <loom.20091012T182258-9@post.gmane.org>
On Mon, Oct 12, 2009 at 6:51 PM, Sal Mangano
<smangano@into-technology.com> wrote:
> 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
This #2 is your best bet by far. An extra blob in each subdir is just
one option, you can handle this "extra metadata" in a number of ways
-- maybe external to git, on a separate history will work best.
The downsides of messing with internal tree handling of git are so
staggering that you'd do better to throw git away.
(this is from experience of abusing git to various purposes that have
little to do with version control :-) )
In other words: Shaun and Dscho are right, so right that it hurts.
hth,
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
next prev parent reply other threads:[~2009-10-12 19:39 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 [this message]
2009-10-12 20:02 ` Salvatore Mangano
2009-10-12 20:24 ` Martin Langhoff
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=46a038f90910121236x6bbe258bwa3bc3fdcc54de524@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).