I've never used Git except for downloading so I don't know, but why do people hate it so bad? -- John H. Reinhardt On 9/4/2020 5:31 PM, Dave McGuire wrote:

I do not think that longer discussions about git are appropriate to have on this list. Sorry for starting this... Paul asked about feedback on switching to git. I just gave a small one-liner, half for fun. I totally do not like git, but if we really want to talk about the why behind it, we should find some other venue for that discussion. Johnny On 2020-09-05 12:24, David Moylan wrote: -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

I hated git when I first had to use it but now I quite like it after getting used to it (and I've had to learn and get used to every CMS/RCS system I've ever used, from RCS to CVS to Subversion to git with ClearCase thrown in there and probably some others I'm not remembering). Some reasons why I didn't like git when I first started using it: 1) the commands are cryptic at first 2) the version is on the entire repository for each commit instead of individual files 3) it was new and I didn't want to learn a new system when I was just trying to get work done 4) Why the hell do we need a new system when we have so many others that are working well? the reasons I like it now: 1) a full git clone makes the clone a full representative of the source repository (with all commit history if extra clone command line options didn't do a shallow clone or something).? This means that you effectively have backups of the repository all over the place in addition to the backups of the server hosting the "official" repository 2) it's powerful enough to do all the diffs, lists, builds, etc from head of any branch, any commit, etc that I need to do when delivering, maintaining, developing complicated software 3) I've now learned it so it's second nature to do what I want to do with it I've experienced two kinds of people at places where git is required (w*rk), those who have no interest or desire to learn about the tools they use and those who want to know all about the tools they use and become proficient with them (and the former generally have to get help from the latter quite often) If course, if you're not forced to learn a new system then it kind of depends upon each person on whether they find that sort of thing useful, maybe fun, maybe interesting or boring and a waste of time. Todd On 9/5/2020 4:23 AM, John H. Reinhardt wrote:

As far as the pyDECnet distribution mechanism goes, my preference would be to distribute the .tar.gz files that can be installed directly with pip3. I have no need for the rest of the development tree, except for the documentation. That could be in a separate zip file, or maybe on a web page somewhere. As for distributing the .tar.gz files, it doesn't really matter - ftp, http, anything I can grab with wget is fine. When it comes to the git vs svn debate, I'd vote for subversion, but that's just because I've used it a lot more. I know how to say "git clone ..." too, and since I'm not planning to make any modifications to pyDECnet that?s really all I need. Bob