[anjuta] Fix some wrong documentation for AnjutaVcsStatus status codes.
- From: James Liggett <jrliggett src gnome org>
- To: svn-commits-list gnome org
- Subject: [anjuta] Fix some wrong documentation for AnjutaVcsStatus status codes.
- Date: Sun, 10 May 2009 02:06:39 -0400 (EDT)
commit 406566639af1d891ae355095e580ef75287959f2
Author: James Liggett <jrliggett cox net>
Date: Sat May 9 22:37:10 2009 -0700
Fix some wrong documentation for AnjutaVcsStatus status codes.
It's not generally true that files can have more than one status in a VCS.
This is only true for Git as far as I can tell, and even then we filter out redundant status information in
this case
---
libanjuta/anjuta-vcs-status.h | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/libanjuta/anjuta-vcs-status.h b/libanjuta/anjuta-vcs-status.h
index f857c7c..4e87df0 100644
--- a/libanjuta/anjuta-vcs-status.h
+++ b/libanjuta/anjuta-vcs-status.h
@@ -29,8 +29,7 @@
* @ANJUTA_VCS_STATUS_MISSING: File is missing
* @ANJUTA_VCS_STATUS_UNVERSIONED: File is ignored by VCS system
*
- * This enumeration is used to specify the status of a file. A file can
- * have multiple status flags assigned (MODIFIED and CONFLICT, for example)
+ * This enumeration is used to specify the status of a file.
*/
typedef enum
{
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]