git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "git list" <git@vger.kernel.org>
Subject: fast-import issues with monotone
Date: Tue, 9 Sep 2008 01:30:39 +0300	[thread overview]
Message-ID: <94a0d4530809081530p60ff8692qbf9c314516d03869@mail.gmail.com> (raw)

Hi,

I'm stuck with yet another issue while trying to export a mtn
repository, so I thought on sharing the list of issues:

a) directory rename/deletes are indistinguishable from files

This means directories must be tracked by the generator to find out if
the operation is on a file, or a directory. If it's in a directory
then the operation should be executed in all the files that are under
that directory.

It's possible to find out the whole tree of a revision, but it's a
*very* expensive operation (takes about a second).

b) file mode changes are just like any other operation (you don't get
the mode at each revision)

This means the file mode needs to be tracked all the time. Also, it
means the file contents (blob) needs to be tracked because sometimes
the only change in the file is the mode.

Again, retrieving the whole tree is possible, but expensive.


There are other issues, but not so important.

For these two issues the only viable solution is to keep track of the
whole tree of each revision. Does it makes sense to do that? Or would
it make more sense to modify fast-import to allow more delta-oriented
operations?

-- 
Felipe Contreras

             reply	other threads:[~2008-09-08 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 22:30 Felipe Contreras [this message]
2008-09-08 22:36 ` fast-import issues with monotone Shawn O. Pearce
2008-09-08 23:37   ` Felipe Contreras

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=94a0d4530809081530p60ff8692qbf9c314516d03869@mail.gmail.com \
    --to=felipe.contreras@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).