From: Pratyush Yadav <me@yadavpratyush.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [GIT PULL] git-gui pull request
Date: Tue, 5 Nov 2019 03:41:15 +0530 [thread overview]
Message-ID: <20191104221115.hinnt47xm4ba3lzy@yadavpratyush.com> (raw)
In-Reply-To: <20191102235006.rpguewvbbpfv4wi5@yadavpratyush.com>
On 03/11/19 05:20AM, Pratyush Yadav wrote:
> Hi Junio,
>
> There are some changes in git-gui since your last pull. With the 2.24
> release coming up, I figure it is a good time to sync up.
>
> The list of changes is a bit misleading. A lot of these changes are
> already in Git's tree, and I retroactively pulled them back in my tree,
> since these bypassed the "main" git-gui tree. Effectively, the merge of
> the commit 60c60b6 should be a no-op. [0] for a reminder.
>
> Sorry for being so late. I didn't realize the release was so close. So
> if this pull request is too much trouble for 2.24, I'm fine if you don't
> pull it now. We can sync up in 2.25 :).
I see that you did manage to do the merge before the 2.24 release.
Thanks.
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2019-11-04 22:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 23:50 [GIT PULL] git-gui pull request Pratyush Yadav
2019-11-04 22:11 ` Pratyush Yadav [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-26 16:10 Pratyush Yadav
2021-02-27 20:47 ` Junio C Hamano
2020-12-18 19:51 Pratyush Yadav
2020-12-19 5:24 ` Junio C Hamano
2020-07-19 9:45 Pratyush Yadav
2020-07-20 19:03 ` Junio C Hamano
2020-05-21 13:12 Pratyush Yadav
2020-05-21 18:08 ` Junio C Hamano
2020-03-19 16:15 Pratyush Yadav
2020-01-08 19:00 Pratyush Yadav
2019-09-17 20:13 Pratyush Yadav
2019-09-17 20:50 ` Denton Liu
2019-09-17 22:51 ` Denton Liu
2019-09-18 19:23 ` 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=20191104221115.hinnt47xm4ba3lzy@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).