You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the spirit of open source, I would like to be able to update the manual to match the changes to the code that I am making. Is it possible to put the file that is the source for the PDF manual in the github repository? That way, each pull request could also include a corresponding update to the manual for cases where the behavior is changed. I don't know what issues there would be with file formats and merging changes, but I think it is worth discussing those issues.
The text was updated successfully, but these errors were encountered:
------ Origineel bericht ------
Van: "Neil MartinsenBurrell" notifications@github.com
Aan: "pa3ang/Tentec506" Tentec506@noreply.github.com
Verzonden: 28-12-2014 23:42:36
Onderwerp: [Tentec506] Putting source file for manual on github (#6)
In the spirit of open source, I would like to be able to update the
manual to match the changes to the code that I am making. Is it
possible to put the file that is the source for the PDF manual in the
github repository? That way, each pull request could also include a
corresponding update to the manual for cases where the behavior is
changed. I don't know what issues there would be with file formats and
merging changes, but I think it is worth discussing those issues.
—
Reply to this email directly or view it on GitHub.
In the spirit of open source, I would like to be able to update the manual to match the changes to the code that I am making. Is it possible to put the file that is the source for the PDF manual in the github repository? That way, each pull request could also include a corresponding update to the manual for cases where the behavior is changed. I don't know what issues there would be with file formats and merging changes, but I think it is worth discussing those issues.
The text was updated successfully, but these errors were encountered: