From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
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 19:38:10 -0600 [thread overview]
Message-ID: <6459a40291a4a_7c682948d@chronos.notmuch> (raw)
In-Reply-To: <xmqqbkiupv4m.fsf@gitster.g>
Junio C Hamano wrote:
> Philip Oakley <philipoakley@iee.email> writes:
> > On 27/03/2023 10:17, Johannes Schindelin wrote:
> >> 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?
> >
> > 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".
> * 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).
Why only those patches?
Does patches signed off by GfW developers carry a special status
regardless of their content?
--
Felipe Contreras
prev parent reply other threads:[~2023-05-09 1:38 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 ` [PATCH 0/2] gitk: handle long command-lines Junio C Hamano
2023-05-09 1:38 ` Felipe Contreras [this message]
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=6459a40291a4a_7c682948d@chronos.notmuch \
--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 \
--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).