Conversation

Notices

1. Nobody [LinuxWalt (@lnxw48a1)] (lnxw48a1@nu.federati.net)'s status on Thursday, 26-Mar-2020 18:52:43 UTC Nobody [LinuxWalt (@lnxw48a1)]

   Remote profile options...

   • Douglas A. Whitfield
   @musicman Yes, I think #git is overly complicated for most projects' needs, but it has mindshare, so people often demand it when another VCS would be more appropriate. It'd be great if transitioning from one to another was a well-understood problem, but it isn't.
   
   Is that #Emacs that is trying to move from #svn to git with #ESR's help and having a difficult time of it?
   • Nobody [LinuxWalt (@lnxw48a1)] (lnxw48a1@nu.federati.net)'s status on Thursday, 26-Mar-2020 19:06:40 UTC Nobody [LinuxWalt (@lnxw48a1)]

     Remote profile options...

     • Douglas A. Whitfield
     I've been lucky enough never to have seen VSS. I've heard mostly negative things about it (though IMO, using a VCS tops not using a VCS, even if that VCS is CVS).
   • Nobody [LinuxWalt (@lnxw48a1)] (lnxw48a1@nu.federati.net)'s status on Thursday, 26-Mar-2020 19:21:15 UTC Nobody [LinuxWalt (@lnxw48a1)]

     Remote profile options...

     • Douglas A. Whitfield
     > This is my point: The last release of Visual SourceSafe was in 2005. In 2019 this customer thought it would be a good idea to switch.
     
     That's pretty risky. I hope someone in your $EMPLOYER can find old docs on the transition process. Surely by now, no one (except your customer) has any VSS experts that could assist if something breaks.