[darcs-users] Request for early user feedback on patch index darcs

[David Leuschner]

Hi Aditya,

thanks for all the work!  I've been using a version built from your
branch since Sunday afternoon and it's feeling fast and worked
smoothly.  It takes a few seconds to build the index for our
branches/repositories but never took too long that it would have been
annoying.

I can't suggest any improvements with the patch index itself but I do
have a very small feature request maybe related to the patch index:
our team often wants to find out how a single file changed over time
and which patches touched it.  We currently use "darcs changes -i
filename" but it's annoying having to search for the file when opening
the patch in the pager.  It would be great if we could just open a
pager with the changes for this single file.

Keep up the good work,

     David


On Sun, Jul 22, 2012 at 6:07 AM, Aditya <bsrkaditya at gmail.com> wrote:
> Hi,
>
>  I am a student participating in Google Summer of Code for darcs. I work on
> an optimization called patch index. I would like to get some feedback on my
> project.
>
>  Patch index improves the speed of changes and annotate commands by quickly
> identifying the patches that modified a given file. This optimization is
> especially useful for large repositories.
>
>  The public repository is at: http://den.darcs.net/Aditya/darcs-patch-index
>
>  Patch index will be automatically created upon get or init.
>
>  If you run changes/annotate/record/.. using patch index darcs on an
> existing repository, patch index will be created automatically.
> Alternatively, run optimize --patch-index to exclusively create patch index.
>
>  You can disable patch index using optimize --no-patch-index, and enable it
> back with optimize --patch-index. If you wish to disable patch index at
> creation, pass --no-patch-index. A lazy get will implicitly disable patch
> index, as you require to have all patches to create a patch index.
>
>  I request users to try patch index darcs, and give feedback on potential ui
> changes, bugs etc
>
>  One of the concerns I already have is automatic creation of patch index on
> existing repositories. The time it takes to create patch index increases
> dramatically based on buffer cache. Creating a patch index just after get
> takes 6 sec, whereas it takes 1min after cleaning the cache(This is for
> darcs development repo). This suggests that a user could experience a
> potentially large delay on changes/record/.. .
>
> BSRK Aditya
>
> _______________________________________________
> darcs-users mailing list
> darcs-users at darcs.net
> http://lists.osuosl.org/mailman/listinfo/darcs-users
>