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
one of the ideals of externpro was that there should be a repository that had the changesets that make the patch/diff -- that developers could look at the commits that went into making a patch and these commits could be reapplied to future work (branching off a new release tag)
however, there have been multiple externpro-style offshoots (which use externpro for it's cmake) that I've been made aware of that take shortcuts and commit a patch file without a repo to back it up
it would be nice if these manually added patch files could be represented in the projects/README.mdpatch/diff column
The text was updated successfully, but these errors were encountered:
currently the
projects/README.md
file is cmake-generated (at cmake-time) from the contents of the projects files themselvesthe
patch/diff
column is populated if thePRO_FOO
variable hasDIFF
,GIT_REF
andGIT_TAG
values - otherwise "none"https://github.com/smanders/externpro/blob/18.01.1/modules/xpfunmac.cmake#L615-L624
one of the ideals of externpro was that there should be a repository that had the changesets that make the patch/diff -- that developers could look at the commits that went into making a patch and these commits could be reapplied to future work (branching off a new release tag)
however, there have been multiple externpro-style offshoots (which use externpro for it's cmake) that I've been made aware of that take shortcuts and commit a patch file without a repo to back it up
it would be nice if these manually added patch files could be represented in the
projects/README.md
patch/diff
columnThe text was updated successfully, but these errors were encountered: