aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/patches
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-04-21 18:18:20 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-04-21 18:18:20 +0100
commit1bf94d0eed3c186692269e4907f2f920a1114250 (patch)
tree947e5da6e311fadf5aa644f75b8b645bf672dd52 /reproduce/software/patches
parentad84e266987a46d88336a23a14ea27100e4cd160 (diff)
README-hacking.md: minor clarifications in checklist
Roberto Baena recently tried building a new project with Maneage and provided the following suggestions to make it more clear for a new user: 1) In the part where we talk about creating a Git repository, we should highlight that it must be empty. This is because some (for example Gitlab) propose to include a `README' file. But if the project is not empty, Git will not allow pushing to it. 2) The `(can be done later)' comment was removed from the "Delete dummy parts") to avoid confusion about applying some of them, but not others: if only some are done, it may cause problems in the build.
Diffstat (limited to 'reproduce/software/patches')
0 files changed, 0 insertions, 0 deletions