From: Junio C Hamano <gitster@pobox.com>
To: "Matthias Aßhauer" <mha1993@live.de>
Cc: "Christian Grün" <christian.gruen@gmail.com>,
git@vger.kernel.org, "Paul Mackerras" <paulus@ozlabs.org>,
"Halil Sen" <halilsen@gmail.com>,
"Stefan Naewe" <stefan.naewe@atlas-elektronik.com>
Subject: Re: Resizing panels in the gitk window
Date: Fri, 06 May 2022 09:23:27 -0700 [thread overview]
Message-ID: <xmqqzgjuocjk.fsf@gitster.g> (raw)
In-Reply-To: <AM0PR04MB6019000A6C54CF97447E7B6EA5C59@AM0PR04MB6019.eurprd04.prod.outlook.com> ("Matthias =?utf-8?Q?A=C3=9Fhauer=22's?= message of "Fri, 6 May 2022 14:00:08 +0200 (CEST)")
Matthias Aßhauer <mha1993@live.de> writes:
> It looks like the issue at [1]. It sadly seems like nobody ever
> reviewed or applied thos suggested patches, but there is some more
> off-list discussion at [2].
>
> [1] https://lore.kernel.org/git/pull.1219.git.git.1645386457.gitgitgadget@gmail.com/#t
> [2] https://github.com/git/git/pull/1219#issuecomment-1113122632
Thanks for a pointer.
I do recall seeing [1] but I do not see anything happened on the
thread since then. I didn't look at it back then primarily because
the patches were made against a wrong history (no, you do not want
to make a gitk patch against my tree nor throw a pull request at my
repository), and there was no way for me to pick it up.
As Documentation/SubmittingPatches says:
Some parts of the system have dedicated maintainers with their own
repositories.
...
Patches to these parts should be based on their trees.
Having said that, gitk has been quiescent for quite a while, and I
wonder if Paul's been too busy for (or no longer interested in)
maintaining it and perhaps he can use a replacement maintainer?
next prev parent reply other threads:[~2022-05-06 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP94bnOyrx6hCmWSjmejVfopUydk10ga42wJzm1M4nk_OXn9Mg@mail.gmail.com>
2022-05-05 7:06 ` Resizing panels in the gitk window Christian Grün
2022-05-06 12:00 ` Matthias Aßhauer
2022-05-06 12:12 ` Christian Grün
2022-05-06 16:23 ` Junio C Hamano [this message]
2022-05-09 12:46 ` Halil SEN
2022-05-09 17:11 ` Junio C Hamano
2022-05-11 8:20 ` Paul Mackerras
2022-05-11 15:08 ` Junio C Hamano
[not found] ` <CAOeUTusOW1=cDKNhrBCzdzfbVLmY_qb7yg114ukRfy904S34uA@mail.gmail.com>
2022-05-11 8:21 ` Paul Mackerras
2022-05-11 15:25 ` Junio C Hamano
2022-05-11 8:17 ` Paul Mackerras
2022-05-06 7:46 ` Christian Grün
2022-05-06 8:32 ` AW: " stefan.naewe
2022-05-06 9:01 ` Christian Grün
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=xmqqzgjuocjk.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.gruen@gmail.com \
--cc=git@vger.kernel.org \
--cc=halilsen@gmail.com \
--cc=mha1993@live.de \
--cc=paulus@ozlabs.org \
--cc=stefan.naewe@atlas-elektronik.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.