From: Felipe Contreras <felipe.contreras@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Paul Mackerras <paulus@ozlabs.org>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Subject: Re: [PATCH 0/2] gitk: handle long command-lines
Date: Mon, 27 Mar 2023 04:17:20 -0600 [thread overview]
Message-ID: <CAMP44s0jG1CQMygMASjEe8Uzu7rOrNuxUbjS05FAA=zBwMV72Q@mail.gmail.com> (raw)
In-Reply-To: <af2111f8-2669-b952-6c4e-45ee0330ec14@gmx.de>
On Mon, Mar 27, 2023 at 3:41 AM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> this patch series saw a positive review from Junio (thank you! I know that
> you try to stay away from Tcl code, so I appreciate the effort very much),
> but apart from that it simply languished on the mailing list for more than
> two months now.
Two months? My patch which contains an obvious fix [1] has been
waiting almost two years.
> Paul, is there anything I can do to help you integrate this into `gitk`?
> Or is it time to pass over `gitk` maintenance to the Git project?
Or just remove it from the Git codebase and maintain it elsewhere.
[1] https://lore.kernel.org/git/20210505211846.1842824-1-felipe.contreras@gmail.com/
--
Felipe Contreras
next prev parent reply other threads:[~2023-03-27 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 11:23 [PATCH 0/2] gitk: handle long command-lines Johannes Schindelin via GitGitGadget
2023-01-24 11:23 ` [PATCH 1/2] gitk: prevent overly long command lines Johannes Schindelin via GitGitGadget
2023-01-24 15:38 ` Junio C Hamano
2023-01-24 11:23 ` [PATCH 2/2] gitk: escape file paths before piping to git log Nico Rieck via GitGitGadget
2023-03-27 9:17 ` [PATCH 0/2] gitk: handle long command-lines Johannes Schindelin
2023-03-27 10:17 ` Felipe Contreras [this message]
2023-05-06 16:00 ` Philip Oakley
2023-05-07 21:35 ` New canonical gitk url Felipe Contreras
2023-05-08 17:53 ` [PATCH 0/2] gitk: handle long command-lines Junio C Hamano
2023-05-09 1:38 ` Felipe Contreras
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='CAMP44s0jG1CQMygMASjEe8Uzu7rOrNuxUbjS05FAA=zBwMV72Q@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=paulus@ozlabs.org \
/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 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).