Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Anything that needs to be filtered for viewing again pretty much needs version control. Email largely fails at that, as hard as other correspondence systems. That said, we have common workflows that use email to build reviewed artifacts.

People love complaining about the email workflow of git, but it is demonstrably better than any chat program for what it is doing.



I don't think I agree with this. Sure, many things should be versioned, but I don't think most correspondence requires it, which is emails primarily purpose.


Agreed if it is correspondence that we are talking about. So, agreed I'm probably too strong that anything needing filtering and such is bad.

I'm thinking of things that are assembled. The correspondence that went into the assembly is largely of historical interest, but not necessarily one of current use.


Yup, I agree there. Email is a horrible means of collaborating on changes in general, but doubly so in realtime. But so is IM.


So you mean like collaborating on a document? Modern word processors are versioned, or you can use text and your own VCS, same as with your code.

Is your issue that you want to discuss the thing you are collaborating on outside of the tool you are creating it in?


This feels inline with my point? Versioning of documents is better done using other tools. Correspondence is fine over email.

We have some tools integrated with email to help version control things. But the actual version control is, strictly, not the emails.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: