Mercurial repository out of sync?
Marcus Hirt
marcus.hirt at datadoghq.com
Mon Jul 27 12:58:56 UTC 2020
Ok. I'll ask for the old mercurial mainline repo to be renamed. How about
jmc -> jmc-old-trunk?
Kind regards,
Marcus
On Mon, Jul 27, 2020 at 2:50 PM Mario Torre <neugens at redhat.com> wrote:
> It should be archived, perhaps by renaming it, but not removed.
>
> The problem is that the repo doesn't say why it's read-only and people
> may have the impression it's synced, or even don't know there's an
> active github repository. The reason why I myself noticed this is
> because I was reported this so it's indeed a source of confusion.
>
> Cheers,
> Mario
>
> On Mon, Jul 27, 2020 at 2:44 PM Marcus Hirt <marcus.hirt at datadoghq.com>
> wrote:
> >
> > Hi Mario,
> >
> > Nope, we closed the mainline repo when we moved over to GitHub. It is
> now read-only. I guess we could remove it if it causes confusion.
> >
> > Kind regards,
> > Marcus
> >
> > On Mon, Jul 27, 2020 at 2:38 PM Mario Torre <neugens at redhat.com> wrote:
> >>
> >> Hi all,
> >>
> >> It seems the mercurial repository is completely out of sync from the
> github one:
> >>
> >> https://hg.openjdk.java.net/jmc/jmc
> >>
> >> While we moved to github I think the jmc mainline should either be
> >> removed (like, deprecated with a note to go visit github) or kept
> >> working with synchronisations to the github source.
> >>
> >> I thought this was done automagically by skara/openjdk infrastructure,
> >> but it seems it's not the case?
> >>
> >> Cheers,
> >> Mario
> >> --
> >> Mario Torre
> >> Associate Manager, Software Engineering
> >> Red Hat GmbH <https://www.redhat.com>
> >> 9704 A60C B4BE A8B8 0F30 9205 5D7E 4952 3F65 7898
> >>
>
>
> --
> Mario Torre
> Associate Manager, Software Engineering
> Red Hat GmbH <https://www.redhat.com>
> 9704 A60C B4BE A8B8 0F30 9205 5D7E 4952 3F65 7898
>
>
More information about the jmc-dev
mailing list