From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.email>,
Paul Mackerras <paulus@ozlabs.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org,
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Subject: Re: [PATCH 0/2] gitk: handle long command-lines
Date: Mon, 08 May 2023 10:53:45 -0700 [thread overview]
Message-ID: <xmqqbkiupv4m.fsf@gitster.g> (raw)
In-Reply-To: fce603aa-ceb7-d601-6a19-657e36d9059c@iee.email
Philip Oakley <philipoakley@iee.email> writes:
> On 27/03/2023 10:17, Johannes Schindelin wrote:
>> Hi Pau & Junio,
>>
>> 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.
>>
>> 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?
>>
>> Ciao,
>> Johannes
>
> I just tripped over this problem while trying to de-stack my Git backlog
> https://github.com/git-for-windows/git/issues/4408 "sdk gitk interaction".
I have done the same "create temporary fork of gitk, queue the
patches, merge the result down while asking Paul to pull from me"
dance I did every once in a while in the past (it seems the last I
did it was in Sep 2019 [*]).
* The last merge from Paulus is ef9b086d (Merge branch 'master' of
git://git.ozlabs.org/~paulus/gitk, 2022-05-11), whose second
parent (i.e. Paulus's tip) was 465f0386 (gitk: include y coord in
recorded sash position, 2022-02-20).
* The two patches that originate from GfW have been applied on top
of 465f0386 in the gitk history; the result of this is 7dd272ec
(gitk: escape file paths before piping to git log, 2023-01-24).
* The js/gitk-fixes-from-gfw topic holds a -Xsubtree=gitk-git merge
of 7dd272ec into my tree. This was merged to 'next' and
hopefully will finish the usual 'next' to 'master' journey
soonish.
Paul, can you fetch js/gitk-fixes-from-gfw branch of
https://github.com/gitster/git/, which will give you 7dd272ec that
you can use to
$ git merge 7dd272ec
to obtain these two commits from Johannes and Nico?
Alternatively, you can fetch 'seen' from any of the mirrors, as it
hopefully should always contain that topic from now on.
Thanks.
[References]
* https://lore.kernel.org/git/xmqqlfum7epn.fsf@gitster-ct.c.googlers.com/
next prev parent reply other threads:[~2023-05-08 17:53 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
2023-05-06 16:00 ` Philip Oakley
2023-05-07 21:35 ` New canonical gitk url Felipe Contreras
2023-05-08 17:53 ` Junio C Hamano [this message]
2023-05-09 1:38 ` [PATCH 0/2] gitk: handle long command-lines 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=xmqqbkiupv4m.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=paulus@ozlabs.org \
--cc=philipoakley@iee.email \
/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 NNTP newsgroup(s).