On 03/05/2018 07:36 PM, Thiago Macieira wrote:
On Monday, 5 March 2018 10:17:56 PST Philippe Coval wrote:
Yes I introduced this "keep json and dat synched feature",
in master while 1.3-rel was branched
Please don't do that. You should not modify checked-in files unless the
developer specifically wants to. I don't know if Nathan was modifying the tool
or if the .dat files were spuriously modified, but that's not relevant.
Instead, I recommend adding a specific command that you run after the tool is
run that copies the .dat files from out/ back into the source dir.
This is what I've done,
it's done by default, but it can be done on purpose
Whoever
runs this command will know about it and will add "updated .dat files" to the
commit message (if it isn't obvious that it was needed).
git status will list the difference
and then developer knows that he introduced a change
then it's his duty to commit and push it.
No one else needs to see those files being modified. Ever.
Well then how will they be updated ?
--
mailto:philippe.co...@osg.samsung.com gpg:0x467094BC
https://blogs.s-osg.org/author/pcoval/
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
