From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: David Reitter <david.reitter@gmail.com>,
Christian Faulhammer <fauli@gentoo.org>,
Joakim.Tjernlund@transmode.se, emacs@gentoo.org,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: Slow start-up on Git trees
Date: Fri, 21 Aug 2009 15:06:16 -0400 [thread overview]
Message-ID: <jwv7hwxj8gb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <200908201915.n7KJFRh5011380@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Thu, 20 Aug 2009 12:15:27 -0700 (PDT)")
> I don't think it's worth it, so I have no interest in working on this,
> but don't let that stop you from doing it.
I think this part should definitely not be asynchronous: all it does is
try to figure out the state of a single file in terms of
"modified/unmodified/removed/added/...". There is no reason why this
should take a long time. So rather than make it asynchronous, I'd say
"make it faster".
> Would commit make sense to be asynchronous? Hmm, maybe, but until
> someone sits down and does it we won't know.
Yes, it does make sense. Actually most VCS operations should be
performed asynchronously. So patches a very welcome in this part of VC
(PCL-CVS already does it all asynchronously, FWIW).
Stefan
next prev parent reply other threads:[~2009-08-21 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 11:23 Slow start-up on Git trees Christian Faulhammer
2009-08-19 20:56 ` Dan Nicolaescu
2009-08-19 21:04 ` David Reitter
2009-08-19 21:11 ` Dan Nicolaescu
2009-08-20 18:46 ` David Reitter
2009-08-20 19:15 ` Dan Nicolaescu
2009-08-21 19:06 ` Stefan Monnier [this message]
2009-08-19 21:54 ` Christian Faulhammer
2009-08-20 7:39 ` Joakim Tjernlund
2009-08-20 8:07 ` Dan Nicolaescu
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=jwv7hwxj8gb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=Joakim.Tjernlund@transmode.se \
--cc=dann@ics.uci.edu \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=emacs@gentoo.org \
--cc=fauli@gentoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.