git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [StGit PATCH] Check for local changes with "goto"
Date: Fri, 30 Jan 2009 17:36:57 +0000	[thread overview]
Message-ID: <b0943d9e0901300936t4a6e0a37x1968a6949fb7bdda@mail.gmail.com> (raw)
In-Reply-To: <20090130152649.GA22044@diana.vm.bytemark.co.uk>

2009/1/30 Karl Hasselström <kha@treskal.com>:
> On 2009-01-30 14:01:20 +0000, Catalin Marinas wrote:
>
>> @@ -706,9 +706,15 @@ class Index(RunWithEnv):
>>                      ).output_one_line())
>>          except run.RunException:
>>              raise MergeException('Conflicting merge')
>> -    def is_clean(self):
>> +    def is_clean(self, tree = None):
>> +        """Check whether the index is clean relative to the given tree."""
>> +        if tree:
>> +            sha1 = tree.sha1
>> +        else:
>> +            sha1 = 'HEAD'
>>          try:
>> -            self.run(['git', 'update-index', '--refresh']).discard_output()
>> +            self.run(['git', 'diff-index', '--quiet', '--cached', sha1]
>> +                    ).discard_output()
>>          except run.RunException:
>>              return False
>>          else:
>
> OK (though I personally would have allowed only Tree objects, with no
> defaulting to the current HEAD).

Done.

See below for an update. I added an __assert_index_worktree_clean()
function in Transaction.

Now, should we add the check_clean argument to Transaction.__init__()
rather than run() as we do for the allow_bad_head case? The check
would need to be done in run() where we have an iw. Just a thought,
I'm not convinced it is better.


diff --git a/stgit/lib/git.py b/stgit/lib/git.py
index e2b4266..07079b8 100644
--- a/stgit/lib/git.py
+++ b/stgit/lib/git.py
@@ -706,9 +706,11 @@ class Index(RunWithEnv):
                     ).output_one_line())
         except run.RunException:
             raise MergeException('Conflicting merge')
-    def is_clean(self):
+    def is_clean(self, tree):
+        """Check whether the index is clean relative to the given treeish."""
         try:
-            self.run(['git', 'update-index', '--refresh']).discard_output()
+            self.run(['git', 'diff-index', '--quiet', '--cached', tree.sha1]
+                    ).discard_output()
         except run.RunException:
             return False
         else:
@@ -858,6 +860,14 @@ class IndexAndWorktree(RunWithEnvCwd):
         cmd = ['git', 'update-index', '--remove']
         self.run(cmd + ['-z', '--stdin']
                  ).input_nulterm(paths).discard_output()
+    def worktree_clean(self):
+        """Check whether the worktree is clean relative to index."""
+        try:
+            self.run(['git', 'update-index', '--refresh']).discard_output()
+        except run.RunException:
+            return False
+        else:
+            return True

 class Branch(object):
     """Represents a Git branch."""
diff --git a/stgit/lib/transaction.py b/stgit/lib/transaction.py
index 54de127..c961222 100644
--- a/stgit/lib/transaction.py
+++ b/stgit/lib/transaction.py
@@ -147,6 +147,11 @@ class StackTransaction(object):
                 'This can happen if you modify a branch with git.',
                 '"stg repair --help" explains more about what to do next.')
             self.__abort()
+    def __assert_index_worktree_clean(self, iw):
+        if not iw.worktree_clean() or \
+           not iw.index.is_clean(self.stack.head.data.tree):
+            self.__halt('Repository not clean. Use "refresh" or '
+                        '"status --reset"')
     def __checkout(self, tree, iw, allow_bad_head):
         if not allow_bad_head:
             self.__assert_head_top_equal()
@@ -183,13 +188,17 @@ class StackTransaction(object):
             self.__checkout(self.__stack.head.data.tree, iw,
                             allow_bad_head = True)
     def run(self, iw = None, set_head = True, allow_bad_head = False,
-            print_current_patch = True):
+            print_current_patch = True, check_clean = False):
         """Execute the transaction. Will either succeed, or fail (with an
         exception) and do nothing."""
         self.__check_consistency()
         log.log_external_mods(self.__stack)
         new_head = self.head

+        # Check for clean index and worktree
+        if check_clean and iw:
+            self.__assert_index_worktree_clean(iw)
+
         # Set branch head.
         if set_head:
             if iw:


-- 
Catalin

  reply	other threads:[~2009-01-30 17:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 23:13 [StGit PATCH] Check for local changes with "goto" Catalin Marinas
2009-01-29  3:45 ` Karl Hasselström
2009-01-30 14:01   ` Catalin Marinas
2009-01-30 15:26     ` Karl Hasselström
2009-01-30 17:36       ` Catalin Marinas [this message]
2009-02-06 14:46         ` Catalin Marinas
2009-02-06 15:31           ` Karl Hasselström
2009-02-06 18:39             ` Catalin Marinas
  -- strict thread matches above, loose matches on Subject: below --
2009-02-10 14:11 Catalin Marinas
2009-02-11  9:05 ` Karl Hasselström
2009-01-14 22:59 Catalin Marinas
2009-01-15  8:37 ` Karl Hasselström
2009-01-15 22:24   ` Catalin Marinas

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

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

  git send-email \
    --in-reply-to=b0943d9e0901300936t4a6e0a37x1968a6949fb7bdda@mail.gmail.com \
    --to=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.com \
    /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.
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 NNTP newsgroup(s).