This is the mail archive of the
mailing list for the GCC project.
Re: Test GCC conversion with reposurgeon available
- From: Joseph Myers <joseph at codesourcery dot com>
- To: <gcc at gcc dot gnu dot org>
- Cc: <esr at thyrsus dot com>
- Date: Thu, 9 Jan 2020 21:56:52 +0000
- Subject: Re: Test GCC conversion with reposurgeon available
- Ironport-sdr: BxpfHCGpW6G06ETfaav3tpdcaI7EOnOpHJ38V/yjj+svkYQte32ngtXWzYcXx0Z/hx8kmfXbCd gfjGIIML/bxfQq/khxPJrF3YSdcHL+C4hcE47ad1WsYx0LMpyvYMZZ9lZRViVpCMRjWGwjEJkp Fp/FiD+5UUErQFfWqOWzCc3RDSenb0C7SCyLKYKGs3Q/BGQVF4NaKRYHzxQY6YWNg0FGqg2pyW hKHCdLZVLPhhZXfqhxhS+w0x9rZtrKwQ8NHc2YevRwEjP4QHsKTHy8wKYOhxR03Jxsk4TRFA3x aic=
- Ironport-sdr: HOHkmIv9herZ2pfG7eeg1Hx6zzQf+7tiNnySOxiKHOfRnnu0Kd80u+NgEGdrDPr9JQuFLOvemY 0tJ4ZkZpEe2vuEA2yoebtFCd6IoHl2rPDR4ESKtdm6SWz6h9+MWa+2wYRV+mYcEt/V9KnwyzLY WLnQgYJHs5T9a0132DauiLU01RmvStWVidhKYRg3j5gNkzZBW3MvGnrrsQn2mPKA1IdDSIoJvg zevljYXc66KpRCTRqy8cWU4eWkA+e3b5W47GHDRVvDL+iGi2cMPPAzKhIkXs/TubdY+xtWlsXW mX8=
- References: <alpine.DEB.email@example.com> <alpine.DEB.firstname.lastname@example.org> <alpine.DEB.email@example.com> <alpine.DEB.firstname.lastname@example.org> <alpine.DEB.email@example.com> <alpine.DEB.firstname.lastname@example.org> <alpine.DEB.email@example.com>
On Thu, 9 Jan 2020, Joseph Myers wrote:
> Here's a test conversion with the conversion machinery in what should be
> essentially final form. This is like the "b" versions (dead and vendor
> branches present but not fetched by default), with the addition of refs
> from the existing git mirror as refs/git-old/* and refs/git-svn-old/* (not
> fetched by default).
Hooks are now set up and ready for testing commits to this repository,
including integration with gcc-cvs and libstdc++-cvs mailing lists and
Bugzilla. I recommend only referencing test bugs you open for the purpose
in commits, not real bugs, to avoid confusing people, as the messages that
end up in Bugzilla don't make it obvious that this is a test conversion
(the messages on the -cvs mailing lists are more obvious, as they say
"gcc-reposurgeon-8" in their subject headers). Commits made in this
repository will not end up in the real conversion. gitweb URLs in
messages from this conversion won't actually work, because they point to
the real gitweb (which currently points to the git-svn mirror).
All commits should generate commit emails. Only commits to master and
release branches should generate Bugzilla updates. master and release
branches do not allow merge commits, other branches do. Branches in
refs/users/<user>/heads and refs/vendors/<vendor>/heads allow
non-fast-forward pushes and branch deletion, other branches don't.
Branch updates or new branches based on the history from the git-svn
mirror (with 3cf0d8938a953ef13e57239613d42686f152b4fe, the initial git-svn
commit, in their ancestry) are disallowed; this avoids someone
accidentally pushing such a branch to a namespace that git fetches by
default and causing everyone to fetch a GB of extra history as a result.
Thus, for continued development based on such a branch you should start by
rebasing (not merging) onto the new version of the history, and then the
rebased branch can be pushed to one of the supported namespaces (under
refs/users/<user>/heads/ if treating it as a user branch, under
refs/heads/devel/ for a development branch that gets fetched by default).
The hook configuration is something that seemed reasonable as a starting
point, not necessarily what we will have as the final configuration. The
configuration file for the AdaCore hooks is project.config on the
refs/meta/config branch (but there are local patches to those hooks at
present, and as with other refs, changes to refs/meta/config will not
persist to the final converted repository).
Joseph S. Myers