From: Birger Skogeng Pedersen <birger.sp@gmail.com>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: Johannes Sixt <j6t@kdbg.org>, Git List <git@vger.kernel.org>
Subject: Re: git-gui: disable the "loose objects popup" dialog?
Date: Thu, 26 Sep 2019 23:12:39 +0200 [thread overview]
Message-ID: <CAGr--=KAv8PQMOUbAh=aAWQeMuvHHacXF=+Mc2-NougLYgr2_A@mail.gmail.com> (raw)
In-Reply-To: <20190926191545.ro7w6lbtlpbyxpk7@yadavpratyush.com>
On Thu, Sep 26, 2019 at 9:15 PM Pratyush Yadav <me@yadavpratyush.com> wrote:
> Talking about auto compression, would it be a better idea to let users
> disable the dialog, and then if they do want auto compression, they can
> just run a cron job (or the Windows equivalent) to do this on their
> repos?
Personally I would prefer that git-gui (silently) performs the check
and compression for me when I open it on a repo. But I can totally see
why some (propbably most) git users would not want that. So I don't
really mind if that part of my proposal gets denied.
> What reasons do people have to have this feature in git-gui,
> instead of running cron jobs?
I can't really think of a reason. But then again I can't really think
of a reason why users would want the "loose objects check" in git-gui
in the first place. Especially not enabled by default, popping up when
the user opens git-gui. A button (manual action) to perform this check
and (if necessary) perform the compression would be better IMO.
Birger
next prev parent reply other threads:[~2019-09-26 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 17:31 git-gui: disable the "loose objects popup" dialog? Birger Skogeng Pedersen
2019-09-26 18:54 ` Johannes Sixt
2019-09-26 19:13 ` Birger Skogeng Pedersen
2019-09-26 19:15 ` Pratyush Yadav
2019-09-26 21:12 ` Birger Skogeng Pedersen [this message]
2019-09-26 21:13 ` Johannes Sixt
2019-10-01 18:00 ` Pratyush Yadav
2019-10-02 7:12 ` Birger Skogeng Pedersen
2019-10-02 18:48 ` Johannes Sixt
2019-10-02 20:41 ` Marc Branchaud
2019-09-26 21:14 ` Marc Branchaud
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='CAGr--=KAv8PQMOUbAh=aAWQeMuvHHacXF=+Mc2-NougLYgr2_A@mail.gmail.com' \
--to=birger.sp@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=me@yadavpratyush.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).