From: Pratyush Yadav <me@yadavpratyush.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Luigi Cantoni <luigic@fgcint.com>,
David Aguilar <davvid@gmail.com>,
git@vger.kernel.org
Subject: Re: Auto Rescan - as plain text
Date: Wed, 10 Jun 2020 14:29:02 +0530 [thread overview]
Message-ID: <20200610085902.uv7cxl6s5qnlniwm@yadavpratyush.com> (raw)
In-Reply-To: <xmqq3673hj11.fsf@gitster.c.googlers.com>
Hi Junio,
On 09/06/20 05:16PM, Junio C Hamano wrote:
> 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.
The feature request is for git-gui, asking for auto rescan in git-gui
like git-cola has. So I think this is the right place for it. Though I
think its easy to miss that on a quick read of the email. I had to do a
double take too :-)
> > 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.
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2020-06-10 8:59 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
2020-06-10 8:59 ` Pratyush Yadav [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200610085902.uv7cxl6s5qnlniwm@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).