They don't have those commits, but they also don't have the commits for the previous release tags in the repo. You can go to any of the release tags, choose a commit to view and you will get a message saying:
> This commit does not belong to any branch on this repository, > and may belong to a fork outside of the repository. You can push a tag to a repo that doesn't already have that commit (or history of commits) in an existing branch, without issue. They are separate projects, but with a shared history. I'd like to be able to go to the apache/solr github and be able to go through the history of a file in different release versions, even if that specific release happened under apache/lucene-solr. - Houston On Tue, Jan 4, 2022 at 2:02 PM Dawid Weiss <dawid.we...@gmail.com> wrote: > > As mentioned in SOLR-15874, we are not hosting the tags for the latest > 8.x releases in the split apache/solr and apache/lucene repositories. All > release tags made prior to the repository split exist in the new repos, so > I see no reason that the newer 8.x tags cannot exist in the new repos as > well. > > I'm not sure I understand - to create a tag you'd need that particular > commit - the "new" repositories for each project don't have those > commits (and arguably shouldn't have since they're, well, separate > projects now). > > Dawid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > >
