From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git for Windows 2.25.1
Date: Thu, 20 Feb 2020 11:16:49 +0530 [thread overview]
Message-ID: <f134ed69-05fb-56f1-5005-db738b6afcd4@gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2002192110230.46@tvgsbejvaqbjf.bet>
Hi Johannes,
-Cc: git-packagers@googlegroups.com, git-for-windows@googlegroups.com
On 20 February 2020 01:40:39 GMT+05:30, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
>The reason for these two glitches is the same as the reason for the
>delay
>(Git v2.25.1 has been released almost four days ago, after all, and I
>try
>to stay relatively close with Git for Windows releases): for technical
>reasons, I had to move the automation that I use to publish new
>versions
>of Git for Windows, and I used this excuse not only to make it public
>(https://dev.azure.com/git-for-windows/git/_build?definitionId=34) but
>also to modernize the pipeline as well as to split it into a build and
>a
>release pipeline.
>
>This required a lot of refactoring of the huge automation shell script
>(https://github.com/git-for-windows/build-extra/blob/master/please.sh),
>and every refactoring has some fallout. On the positive side, the new
>pipelines should be more robust and a lot faster, too.
>
That's a good thing despite the minor fallout.
> Here's hoping that future releases go smoother than this one :-)
Thanks a lot for your relentless efforts to make Git-for-Windows better!
>Thanks,
>Johannes
>
I haven't noticed you sign using your real name before that I had a mild
suspicion if this was really you or one of your automaton's gone rogue
;-) Just now realized that you sign all your Git-for-Windows release
e-mails this way.
--
Sivaraam
prev parent reply other threads:[~2020-02-20 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 18:53 [ANNOUNCE] Git for Windows 2.25.1 Johannes Schindelin
2020-02-19 20:10 ` Johannes Schindelin
2020-02-20 5:46 ` Kaartic Sivaraam [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
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=f134ed69-05fb-56f1-5005-db738b6afcd4@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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.
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).