From 2495bc8e5da6946c6524d317951ff9b48c1a9831 Mon Sep 17 00:00:00 2001 From: risk danger olson Date: Thu, 2 Feb 2017 08:47:34 -0700 Subject: [PATCH] docs: Address ttaylorr's comments --- docs/api/batch.md | 2 +- docs/api/locking.md | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/api/batch.md b/docs/api/batch.md index 496d68e0..60008f40 100644 --- a/docs/api/batch.md +++ b/docs/api/batch.md @@ -1,6 +1,6 @@ # Git LFS Batch API -Added: v1.0 +Added: v0.6 The Batch API is used to request the ability to transfer LFS objects with the LFS server. The Batch URL is built by adding `/objects/batch` to the LFS server diff --git a/docs/api/locking.md b/docs/api/locking.md index 14eb6cb1..40285825 100644 --- a/docs/api/locking.md +++ b/docs/api/locking.md @@ -60,8 +60,9 @@ Successful responses return the created lock: * `id` - String ID of the Lock. Git LFS doesn't enforce what type of ID is used, as long as it's returned a string. -* `path` - String path name of the locked file. -* `locked_at` - The String timestamp the lock was created. +* `path` - String path name of the locked file. This should be relative to the +root of the repository working directory. +* `locked_at` - The string ISO 8601 formatted timestamp the lock was created. * `committer` - The optional name/email of the user that created the Lock. This could be different from the `committer` values in the request if the lock service already knows the committer's identity based on the API credentials.