From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Outdated git-review package
Date: Sat, 23 Jul 2022 16:31:50 +0100 [thread overview]
Message-ID: <CA+kUOakUN+T54XFuZkVudHpqYWPUpgKb92neT9DuqGZczMh1eQ@mail.gmail.com> (raw)
In-Reply-To: <93083779-5f38-7f41-0c93-512573842ddd@gmail.com>
On Wed, 20 Jul 2022 at 19:37, Marco Atzeri wrote:
> On 20.07.2022 10:07, Adam Dinwoodie wrote:
> > On Wed, Jul 13, 2022 at 08:44:22AM +0000, Oledzki, Maciej (Nokia - PL/Wroclaw) wrote:
> >> Hi,
> >>
> >> Latest git-review package available in Cygwin repository (2.1.0-1) is not compatible with latest git package (2.37.0-1).
> >> Following error appears in during gerrit review:
> >>
> >> Errors running git rebase -p -i remotes/gerrit/master
> >> fatal: --preserve-merges was replaced by --rebase-merges
> >>
> >> This problem is fixed in git review 2.2.0:
> >> https://docs.opendev.org/opendev/git-review/latest/releasenotes.html#relnotes-2-2-0
> >>
> >> It would be great if version 2.2.0 (or more recent) of git-review was available.
> >
> > Marco, are you able to get this updated?
>
> 2.3.1 is going up.
>
> Curious, I forgot I was the maintainer I thought it was you
If you want to hand that over to me to look after along with the other
Cygwin Git bits I handle, I'm happy to do that! I don't use Gerrit
myself, so I don't have any good way of testing the packages, but it's
a sufficiently simple package that I'm fine to just keep it up to date
myself anyway.
next prev parent reply other threads:[~2022-07-23 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 8:44 Oledzki, Maciej (Nokia - PL/Wroclaw)
2022-07-20 8:07 ` Adam Dinwoodie
2022-07-20 18:36 ` Marco Atzeri
2022-07-23 15:31 ` Adam Dinwoodie [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-18 11:22 Oledzki, Maciej (Nokia - PL/Wroclaw)
2021-05-18 19:52 ` Marco Atzeri
2021-05-19 8:50 ` Oledzki, Maciej (Nokia - PL/Wroclaw)
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=CA+kUOakUN+T54XFuZkVudHpqYWPUpgKb92neT9DuqGZczMh1eQ@mail.gmail.com \
--to=adam@dinwoodie.org \
--cc=cygwin@cygwin.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.
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).