With some time passed and no-one opposed, I'll file a ticket to switch
us to Git.
On 06/03/2022 13.45, Greg Stein wrote:
+1
Rich expressed a desire to retain history in the git repository (rather
than two histories), and I agree with that thought. It "should" be pretty
easy to just rebuild the .git, and mark svn readonly.
Implied: happy to see svn become readonly today (and detach any sync'ing to
git). I doubt any of us wants to commit to svn in the next week or so.
Cheers,
-g
On Sun, Mar 6, 2022 at 5:52 AM Daniel Gruno <[email protected]> wrote:
On 06/03/2022 12.33, Daniel Gruno wrote:
Hi folks,
As per suggestion from Greg, I think we should keep the existing
steve.git repository but start a fresh main branch for the new code.
This would mean keeping the old subversion history in the trunk branch
for those interested.
We'd also be putting the web site into this repository, as pelican
thankfully knows how to work with that compartmentalized.
Thoughts? Since this is a technical change, I'd love two or three other
+1s on this.
With regards,
Daniel.
upon further reflection, it might be prudent to redo the steve mirror
and get the full subversion history. currently only pysteve is present
in our git mirror, I'd like to have the full history there before the
switch.
What we could actually do is continue on trunk, but move the old stuff
to a sub-directory...
Any objections?
