- Ursprungligt meddelande -
That configurability is a slipperly slope to drag us into giving
users
more complexity that does not help them very much, I suspect.
Earlier somebody mentioned size and mtime is often enough, so I
think a single option core.looseStatInfo (substitute
Robin Rosenberg robin.rosenb...@dewire.com writes:
- Ursprungligt meddelande -
That configurability is a slipperly slope to drag us into giving
users
more complexity that does not help them very much, I suspect.
Earlier somebody mentioned size and mtime is often enough, so I
Junio C Hamano wrote:
Robin Rosenberg robin.rosenb...@dewire.com writes:
That configurability is a slipperly slope to drag us into giving users
more complexity that does not help them very much, I suspect.
Earlier somebody mentioned size and mtime is often enough, so I
think a single
Robin Rosenberg robin.rosenb...@dewire.com writes:
I'd say a simplistic ignore if zero is stored or even ignore this
as one of the systems that shares this file writes crap in it may
be sufficient, and if this is a jGit specific issue, it might even
make sense to introduce a single
Robin Rosenberg robin.rosenb...@dewire.com writes:
diff --git a/read-cache.c b/read-cache.c
index fda78bc..f7fe15d 100644
--- a/read-cache.c
+++ b/read-cache.c
@@ -197,8 +197,9 @@ static int ce_match_stat_basic(struct cache_entry *ce,
struct stat *st)
}
if (ce-ce_mtime.sec !=
Robin Rosenberg robin.rosenb...@dewire.com writes:
@@ -566,6 +566,31 @@ static int git_default_core_config(const char *var,
const char *value)
trust_ctime = git_config_bool(var, value);
return 0;
}
+ if (!strcmp(var, core.ignorezerostat)) {
+
- Ursprungligt meddelande -
Robin Rosenberg robin.rosenb...@dewire.com writes:
diff --git a/read-cache.c b/read-cache.c
index fda78bc..f7fe15d 100644
--- a/read-cache.c
+++ b/read-cache.c
@@ -197,8 +197,9 @@ static int ce_match_stat_basic(struct
cache_entry *ce, struct
Robin Rosenberg robin.rosenb...@dewire.com writes:
Semantically they're somewhat different. My flags are for ignoring
a value when it's not used as indicated by the value zero, while
trustctime is for ignoring untrustworthy, non-zero, values.
Yeah, I realized that after writing that message.
Is this the user edits in eclipse and then runs 'git status' from
the
terminal problem?
Yes. Of course not just status, but any command that validates
the index. On Unix this is usually bearable, though slow, but on
Windows I often see git status take minutes (yes large files...).
-- robin
Am 1/15/2013 1:11, schrieb Junio C Hamano:
I'd say a simplistic ignore if zero is stored or even ignore this
as one of the systems that shares this file writes crap in it may
be sufficient, and if this is a jGit specific issue, it might even
make sense to introduce a single configuration
- Ursprungligt meddelande -
Robin Rosenberg robin.rosenb...@dewire.com writes:
Semantically they're somewhat different. My flags are for ignoring
a value when it's not used as indicated by the value zero, while
trustctime is for ignoring untrustworthy, non-zero, values.
Yeah,
11 matches
Mail list logo
