git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git List <git@vger.kernel.org>
Subject: Re: [GIT PULL v2] git-gui pull request
Date: Thu, 4 Mar 2021 13:54:05 -0500	[thread overview]
Message-ID: <CAPig+cR8WA-KpuBsOjqbR2yGMwiszwe_ZEeQzpV-DutCh0aaww@mail.gmail.com> (raw)
In-Reply-To: <20210304184455.sah45hzavctfnhwa@yadavpratyush.com>

On Thu, Mar 4, 2021 at 1:45 PM Pratyush Yadav <me@yadavpratyush.com> wrote:
> In light of the recent breakages on macOS, this PR contains a revert of
> the offending commit. I will add it back in the next version with
> problems on macOS fixed.
>
> This highlights the need for me to figure out a way to test on macOS. It
> is not a good strategy to put breaking bugs in a release and hope to fix
> it in the next one. And macOS has been a regular offender. Dunno if it
> is possible without owning the Mac hardware though...

A couple suggestions:

Send pull requests to Junio early and often. His tree gets tested more
widely than the stand-alone git-gui, so breakage is more likely to get
detected earlier rather than later in his tree, thus giving us a more
comfortable margin for dealing with problems.

The majority of the problems noticed on macOS have not been specific
to macOS itself. Rather, they are specific to the old version of Tcl
which ships with macOS. Therefore, an easy way for you to detect these
problems early is to install an old version of Tcl on your development
machine and ensure that you test against that version before sending a
pull request. I think that this approach alone would catch all of the
outright breakage problems we've seen recently on macOS. (It won't
catch aesthetic issues, but those tend to be minor compared with the
outright breakage.)

Thanks.

  reply	other threads:[~2021-03-04 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 18:44 [GIT PULL v2] git-gui pull request Pratyush Yadav
2021-03-04 18:54 ` Eric Sunshine [this message]
2021-03-04 21:04 ` Junio C Hamano

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=CAPig+cR8WA-KpuBsOjqbR2yGMwiszwe_ZEeQzpV-DutCh0aaww@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).