@Matthieu
Ok, I'm replacing with "Reset only files which actually changed (not
those with only stat information change)"
@Junio
I'm not sure what you're asking, sorry, I'm not able to understand
your question.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a mes
Ok, this is how it looks. If everything is ok, I'm sending it to the ML
>From 262bdfb5cc84fec7c9b74dc92bb604f9d168ef9a Mon Sep 17 00:00:00 2001
From: Alexander Nestorov
Date: Wed, 19 Jun 2013 09:55:42 +0200
Subject: [PATCH] Add example for reseting based on content changes instead
How about that:
+Reset only files who's content changed (instead of mtime modification)::
++
+
+$ git update-index --refresh <1>
+$ git reset --hard <2>
+
++
+<1> Make git realize which files actually changed instead of
+checking out al
I'm home,
https://github.com/alexandernst/git/commit/61f0a7d558e3cbae308fabdff66bd87569d6aa18
Is that good? Should I PR?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-
Sorry for not keeping everyone Cced, I wasn't aware of the rules.
Yes, writing about that in the docs seems more reasonable than patching reset,
as as you said, that'd just run update-index before the reset.
Let me get at home and I'll try to push a change :)
Regards
--
To unsubscribe from this l
Indeed, "git update-index --refresh" before "git reset" did the trick :)
Anyways, what about the proposal? Should it be implemented?
Thank you
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger
Git reset --keep is not an option as it will abort the operation if
there are local changes,
which is exactly what I want to do: replace files with local changes
but leave file
permissions as they are.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to maj
Git does preserve file permissions, that is, git is aware of the
permissions you can set with chmod.
I'm not trying to ignore the x bit, what I'm trying to do is make
"git reset" checkout only the files that actually changed instead
of checking out all the files with different permissions than the
Recently I had to write some automation scripts and I found
that git reset --hard actually restores each file's permissions.
That is causing both the created and the last-modified dates
of the file to get changed to the time of the git reset.
This behavior is easy to demonstrate:
echo "test" > m
9 matches
Mail list logo
