summaryrefslogtreecommitdiff
path: root/issues/i_b19d5ada.cil
diff options
context:
space:
mode:
authorFrancois Marier <francois@debian.org>2008-06-29 21:52:52 +1200
committerFrancois Marier <francois@debian.org>2008-06-29 21:53:41 +1200
commit41ec963c1aace994072b6d62b20cdce5370e0e8e (patch)
tree487b4918b4ecce530f214212271382cbb801f1b2 /issues/i_b19d5ada.cil
parent1893ee23dbc1f69d9dd3b03b4d28f89003762d3d (diff)
parent03a60521d41962fb3d36e8e8002e9bba51796ff6 (diff)
Merge commit 'upstream/v0.3.0'
Conflicts: bin/cil
Diffstat (limited to 'issues/i_b19d5ada.cil')
-rw-r--r--issues/i_b19d5ada.cil24
1 files changed, 24 insertions, 0 deletions
diff --git a/issues/i_b19d5ada.cil b/issues/i_b19d5ada.cil
new file mode 100644
index 0000000..7eb3b56
--- /dev/null
+++ b/issues/i_b19d5ada.cil
@@ -0,0 +1,24 @@
+Summary: Add a 'cil check-in-git' command
+Status: New
+CreatedBy: Andrew Chilton <andychilton@gmail.com>
+AssignedTo: Andrew Chilton <andychilton@gmail.com>
+Label: Milestone-Future
+Label: Release-v0.2.1
+Label: Type-Enhancement
+Inserted: 2008-06-24T03:24:14
+Updated: 2008-06-27T13:29:00
+
+The ability to check whether issues/comments/attachments are tracked by Git is
+important. Or indeed any VCS system.
+
+My thoughts are that this command would do something like the following:
+
+* internally, it runs "git ls-files issues/" and makes a list of files in that
+ directory
+* makes a list of issues that are currently contained in the directory
+* complains if it finds something Git doesn't know about
+
+Also, when it runs through each issue, it should do the same for all comments
+and attachments. It could either output something which tells you you have
+untracked files or it could give you example git commands which add them to
+those being tracked.