From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2018, #04; Mon, 30)
Date: Wed, 02 May 2018 19:46:27 +0900 [thread overview]
Message-ID: <xmqqlgd2uygs.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1805020850400.73@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 2 May 2018 08:53:16 +0200 (DST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> As I wrote elsewhere, for a low-impact and ralatively old issue like
>> this, it is OK for a fix to use supporting code that only exists in
>> more recent codebase and become unmergeable to anything older than
>> the concurrent 'maint' track as of the time when the fix is written.
>> Even though it is sometimes nicer if the fix were written to be
>> mergeable to codebase near the point where the issue originates, it
>> is often not worth doing so if it requires bending backwards to
>> refrain from using a newer and more convenient facility.
>
> So do you want me to clean up the backporting branches? I mean, we could...
For a relatively obscure and low-impact bug that is old like this
one, I'd actually prefer to be able to say "heh, if that hurts,
either refrain from doing so, or update to the recent maintenance
track that has a fix for it", to use the fix as an incentive to move
the world forward ;-). After all, people have lived with the bug
for a long time.
next prev parent reply other threads:[~2018-05-02 10:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 3:25 What's cooking in git.git (Apr 2018, #04; Mon, 30) Junio C Hamano
2018-04-30 15:33 ` SZEDER Gábor
2018-05-01 13:46 ` Johannes Schindelin
2018-05-02 3:59 ` Junio C Hamano
2018-05-02 6:53 ` Johannes Schindelin
2018-05-02 10:46 ` Junio C Hamano [this message]
2018-05-02 1:36 ` Junio C Hamano
2018-04-30 19:17 ` js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)] Johannes Sixt
2018-05-01 11:57 ` Johannes Schindelin
2018-05-01 14:58 ` Johannes Sixt
2018-05-01 18:10 ` Eric Sunshine
2018-05-02 1:43 ` js/no-pager-shorthand [ Junio C Hamano
2018-05-01 18:46 ` js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)] Ævar Arnfjörð Bjarmason
2018-05-02 23:17 ` What's cooking in git.git (Apr 2018, #04; Mon, 30) Brandon Williams
2018-05-04 18:04 ` Elijah Newren
2018-05-07 4:39 ` 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=xmqqlgd2uygs.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=szeder.dev@gmail.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).