git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alexander Nestorov <alexandernst@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git <git@vger.kernel.org>
Subject: Re: [Request] Git reset should be able to ignore file permissions
Date: Wed, 19 Jun 2013 10:00:04 +0200	[thread overview]
Message-ID: <CACuz9s0jqe9zErBLZ5+kv2OCKW5fFHq0sifc2GS=n4jFpDiQZw@mail.gmail.com> (raw)
In-Reply-To: <vpqsj0emzdu.fsf@anie.imag.fr>

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 <alexandernst@gmail.com>
Date: Wed, 19 Jun 2013 09:55:42 +0200
Subject: [PATCH] Add example for reseting based on content changes instead of
 stat changes

---
 Documentation/git-reset.txt | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt
index a404b47..da639e9 100644
--- a/Documentation/git-reset.txt
+++ b/Documentation/git-reset.txt
@@ -289,6 +289,18 @@ $ git reset --keep start                    <3>
 <3> But you can use "reset --keep" to remove the unwanted commit after
     you switched to "branch2".

+Reset only files who's content changed (instead of stat information)::
++
+------------
+$ git update-index --refresh               <1>
+$ git reset --hard                         <2>
+------------
++
+<1> Make Git realize which files actually changed instead of
+checking out all files whether their content changed or only
+their mtime changed.
+<2> Now git reset --hard will checkout only the files that
+actually changed.

 DISCUSSION
 ----------
--
1.8.1.msysgit.1

  reply	other threads:[~2013-06-19  8:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 13:25 [Request] Git reset should be able to ignore file permissions Alexander Nestorov
2013-06-18 13:34 ` Matthieu Moy
2013-06-18 13:48   ` Alexander Nestorov
2013-06-18 14:06     ` Matthieu Moy
2013-06-18 14:22       ` Alexander Nestorov
2013-06-18 14:33         ` Matthieu Moy
2013-06-18 14:39           ` Alexander Nestorov
2013-06-18 15:51             ` Alexander Nestorov
2013-06-18 16:00               ` Matthieu Moy
2013-06-18 17:03                 ` Alexander Nestorov
2013-06-19  5:40                   ` Matthieu Moy
2013-06-19  8:00                     ` Alexander Nestorov [this message]
2013-06-19 11:37                       ` Matthieu Moy
2013-06-19 18:43                         ` Junio C Hamano
2013-06-20 13:28                           ` Alexander Nestorov
2013-06-19 16:40                       ` Hilco Wijbenga
2013-06-18 14:01 ` John Keeping
2013-06-18 14:05   ` Alexander Nestorov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACuz9s0jqe9zErBLZ5+kv2OCKW5fFHq0sifc2GS=n4jFpDiQZw@mail.gmail.com' \
    --to=alexandernst@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).