Re: [StGit PATCH 03/14] Write to a stack log when stack is modified

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Karl
Date: Tuesday, July 1, 2008 - 1:13 pm

On 2008-06-17 17:32:47 +0200, Karl Hasselström wrote:


I had an even better idea: no default value. Every caller gets to say
either log = True or log = False, which makes it immediately obvious
to the reader. (That is, every caller still using the old
infrastructure; with the new infrastructure, we log if and only if a
transaction is run.)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[StGit PATCH 00/14] Undo series, Karl , (Wed Jun 11, 10:34 pm)
[StGit PATCH 01/14] Fix typo, Karl , (Wed Jun 11, 10:34 pm)
[StGit PATCH 05/14] New command: stg reset, Karl , (Wed Jun 11, 10:34 pm)
[StGit PATCH 06/14] Log conflicts separately, Karl , (Wed Jun 11, 10:34 pm)
[StGit PATCH 11/14] New command: stg undo, Karl , (Wed Jun 11, 10:35 pm)
[StGit PATCH 12/14] New command: stg redo, Karl , (Wed Jun 11, 10:35 pm)
Re: [StGit PATCH 03/14] Write to a stack log when stack is ..., Karl , (Tue Jul 1, 1:13 pm)