latest 9 messages by Wes-
+
[2020-04-23T13:30:06Z]
Wes-
holgersson: You're not the only one. I've been around long enough that I remember the fiasco that happened when they bought hotmail...took them YEARS to get it working right on Windows NT.
+
[2020-04-23T13:29:27Z]
Wes-
holgersson: Ah. Yes. If you can receive e-mail from gmail users, perhaps you could set up a gmail account and forward mail from that account, which originates from github, to your main account? Then point github at your gmail.
+
[2020-04-23T13:26:19Z]
Wes-
holgersson: I have zero issues with gmail. Are you trying to run a local MTA?
+
[2020-04-23T13:23:59Z]
Wes-
microsoft bought github?! Holy Crap. I guess the days of MS hating "open sores" is gone!
+
[2020-04-23T13:22:56Z]
Wes-
*nod* - what I like, honestly, is that it gives an easy-to-see delta from the mainline. Although, now I'm curious how a non-master default branch will play with npm. I guess the best thing to do is to try it and see. :)
+
[2020-04-23T13:15:23Z]
Wes-
Hm - this sounds like a good way to go. Thanks. I'll be ready for release shortly, might as well start this off on the right foot.
+
[2020-04-23T13:14:04Z]
Wes-
jhass - if I stay on the feature branch, can I make the "default view" on github be the feature branch? Otherwise, users will get the wrong readme.
+
[2020-04-23T12:57:58Z]
Wes-
cts unlikely)
+
[2020-04-23T12:57:58Z]
Wes-
Mornin' folks -- looking for some advice. I've forked a project on github, and my changes will /not/ make it into mainline. What is the best way for me to set up my workflow so that I can track changes from the mainline? I normally do my work on feature branches and merge back to master. Do I keep this up, and just keep merging from the mainline master, or is there a smarter way? (My changes are surgical, difficult merge confli