All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Luigi Cantoni <luigic@fgcint.com>, David Aguilar <davvid@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Auto Rescan - as plain text
Date: Tue, 09 Jun 2020 17:16:42 -0700	[thread overview]
Message-ID: <xmqq3673hj11.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <36bd7dc26883017770c28da94a251be2d5019f75.camel@fgcint.com> (Luigi Cantoni's message of "Wed, 10 Jun 2020 08:09:26 +0800")

Luigi Cantoni <luigic@fgcint.com> writes:

> Hi All,
> I have been using git for several years now and using git-cola.
> I just started up git gui and that is quite self explanatory and all
> the functions I use with git-cola appear to be there.

We used to see the maintainer of that project around here quite
frequently but haven't seen him for a while [jch: David Cc'ed].

By reading https://git-cola.github.io/about.html it seems that they
prefer to see problem reports and feature requests at
https://github.com/git-cola/git-cola/issues and not on this list.

>
> One thing I liked in git-cola was that it very quickly reflected my
> changes in its display window.
> I have looked in the options and I cannot see either a flag to set it
> to auto rescan or set a time for the auto rescan.
>
> Have I missed it and there is a way turn this on or give it a shorter
> time (if in fact it is does do it).
> If it is not offered could it become an option.
> I can see that some people may not feel the overhead for distributed
> system is worth having this on so they would want if off.
> It is not critical (just nice) as I know I can
> 1) rescan
> or 2) go off the file and back on again.
> It then displays the correct diff/updated contents.
>
> Thanks for any advise or help.
> -- 
>
> Thanks
> Luigi Cantoni
> M: +61 421 624 804
> T: +61 8 9418 3777
> Email: luigic@fgcint.com

  reply	other threads:[~2020-06-10  0:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37bd22ee8bcb9c91969d68cbc5e6852a8a70ab36.camel@fgcint.com>
     [not found] ` <bf895dc550881b35baea45cd269bf9b0518ade35.camel@fgcint.com>
     [not found]   ` <816ce248ab1708d41b5233abdb998ff2d4cb3400.camel@fgcint.com>
2020-06-10  0:09     ` Auto Rescan - as plain text Luigi Cantoni
2020-06-10  0:16       ` Junio C Hamano [this message]
2020-06-10  8:59         ` Pratyush Yadav
2020-06-10 16:57           ` Junio C Hamano
2020-06-30  6:37           ` David Aguilar
2020-06-10  8:51       ` Pratyush Yadav

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=xmqq3673hj11.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=luigic@fgcint.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 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.