Keith, ________________________________________ From: lilypond-devel-bounces+james.lowe=datacore....@gnu.org [lilypond-devel-bounces+james.lowe=datacore....@gnu.org] on behalf of Keith OHara [k-ohara5...@oco.net] Sent: 24 June 2011 03:31 To: lilypond-devel@gnu.org Subject: Re: question about mod dates in my git tree for resetted files
James Lowe <James.Lowe <at> datacore.com> writes: > > I made the patch and then aborted my changes. > I noticed however that the mod dates were still the same as the time > I made the patch, even though the files themselves are the original files That is normal. The file system reports the last time the file changed, which is probably the moment you aborted the changes. Your patch for tab-conversion consistently shows the old versions removed, but no new versions put in their place --- it's not just the side-by-side view. I have no guesses about what might have gone wrong. If you are curious, maybe wade in to the command line just a bit and try `git status` just after re-committing your tab-expand changes (which might tell you the new versions are modified but not added or something; I don't know) ----------------------- Thanks for that. I went back and redid my edits (see other email I just sent out). I don't know what happened, but it's good to get some sanity check. I did a git status before committing and it showed all the .py files that were modified and after the commit they were gone. As opposed to git status showing files that need to be 'added' (a la binary files). Oh well, I seemed to have sorted this out. James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
