summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Shumaker <lukeshu@lukeshu.com>2017-04-24 12:59:40 -0400
committerLuke Shumaker <lukeshu@lukeshu.com>2017-04-24 12:59:40 -0400
commiteb3af91d96b13173580233a9e0df0ccdcd505dcd (patch)
tree96710da5041877189b72eb7e87f2b6d974d33811
parent9f6e69951b75b16a97c70b2cc9bc5fe4562e43ce (diff)
autobuild.sh: tidy a comment
-rwxr-xr-x.local/bin/autobuild.sh10
1 files changed, 6 insertions, 4 deletions
diff --git a/.local/bin/autobuild.sh b/.local/bin/autobuild.sh
index a501b6e..009cbf7 100755
--- a/.local/bin/autobuild.sh
+++ b/.local/bin/autobuild.sh
@@ -26,10 +26,12 @@ main() {
. "$(librelib messages)"
setup_traps
- # Get the date as the *very* first thing We get the current date instead
- # of getting a date from git because git time is non-monotonic. I mean,
- # the system time is also non-monotonic. But at day-granularity, I
- # don't expect this to ever come up. A git-rebase or a weird merge
+ # Get the date as the *very* first thing.
+ #
+ # We get the current date instead of getting a date from git
+ # because git time is non-monotonic. (I mean, the system time
+ # is also non-monotonic. But at day-granularity, I don't
+ # expect that to ever come up.) A git-rebase or a weird merge
# could easily break things if we get the git time.
newpkgver_date=$(LC_ALL=C date -u +%Y%m%d)