On Jul 25, 2006, Gerd wrote:
On Jul 24, 2006, at 6:14 PM, Brad Choate wrote:
The second one sounds as if you have a file or files selected in the project drawer that have no local changes.
They do, svn on the command line, or using the svn bundle with one of the changed files selected in TM works fine. It is just the "Subversion Status" panel from which it doesn't work.
Gerd
Has this been fixed/addressed yet? I've checked the archives but I can't seem to find a resolution. I'm still getting the "File(s) not modified; nothing to commit." when I try to 'Commit' from the SVN 'Status' window. I'm fully up to date with the app (cutting edge) and the svn repository. And yes, I do have the top level folder of the project selected when I run the 'Status' command.
Carpe viam, Mike
Michael Larocque Chief Cook and Bottle Washer Prolumina Communications Inc. http://prolumina.com/~mlarocque/
On 4/8/2006, at 4:47, Michael Larocque wrote:
The second one sounds as if you have a file or files selected in the project drawer that have no local changes.
They do, svn on the command line, or using the svn bundle with one of the changed files selected in TM works fine. It is just the "Subversion Status" panel from which it doesn't work.
Has this been fixed/addressed yet? I've checked the archives but I can't seem to find a resolution. I'm still getting the "File(s) not modified; nothing to commit." when I try to 'Commit' from the SVN 'Status' window [...]
We talked shortly about it on IRC iirc and the problem is that the commit from the status window uses the project folder (not the selection in the drawer) meaning that if your project folder itself is not the one under svn (but instead a sub folder is) then the problem will arise.
There was no simple fix for this -- I think a bit of refactoring is called for before doing too much more patching of this status window.
On 2006-Aug-04, at 10:02, Allan Odgaard wrote:
We talked shortly about it on IRC iirc and the problem is that the commit from the status window uses the project folder (not the selection in the drawer) meaning that if your project folder itself is not the one under svn (but instead a sub folder is) then the problem will arise.
Hmmm, that's strange, because the project folder _is_ under svn.
There was no simple fix for this -- I think a bit of refactoring is called for before doing too much more patching of this status window.
That's cool. I was wondering if I had something set up incorrectly.
Carpe viam, Mike
Michael Larocque Chief Cook and Bottle Washer Prolumina Communications Inc. http://prolumina.com/~mlarocque/
On Aug 4, 2006, at 12:02 PM, Allan Odgaard wrote:
On 4/8/2006, at 4:47, Michael Larocque wrote:
The second one sounds as if you have a file or files selected in the project drawer that have no local changes.
They do, svn on the command line, or using the svn bundle with one of the changed files selected in TM works fine. It is just the "Subversion Status" panel from which it doesn't work.
Has this been fixed/addressed yet? I've checked the archives but I can't seem to find a resolution. I'm still getting the "File(s) not modified; nothing to commit." when I try to 'Commit' from the SVN 'Status' window [...]
We talked shortly about it on IRC iirc and the problem is that the commit from the status window uses the project folder (not the selection in the drawer) meaning that if your project folder itself is not the one under svn (but instead a sub folder is) then the problem will arise.
There was no simple fix for this -- I think a bit of refactoring is called for before doing too much more patching of this status window.
There does seem to be a simple fix (svn 4554), but it required a slight modification to svn_commit to accept files on the command line in graphical mode.
format_status does need refactoring -- in two languages.
Chris
On Aug 4, 2006, at 8:27 PM, Chris Thomas wrote:
There does seem to be a simple fix (svn 4554), but it required a slight modification to svn_commit to accept files on the command line in graphical mode.
Thanks SO much for fixing that! :D
format_status does need refactoring -- in two languages.
Quite so. My additions may be mostly functional, but the code is not up to my usual standards of production quality stuff. :(
Chris
thomas Aylott—subtleGradient
On Aug 3, 2006, at 9:47 PM, Michael Larocque wrote:
On Jul 25, 2006, Gerd wrote:
On Jul 24, 2006, at 6:14 PM, Brad Choate wrote:
The second one sounds as if you have a file or files selected in the project drawer that have no local changes.
They do, svn on the command line, or using the svn bundle with one of the changed files selected in TM works fine. It is just the "Subversion Status" panel from which it doesn't work.
Gerd
Has this been fixed/addressed yet? I've checked the archives but I can't seem to find a resolution. I'm still getting the "File(s) not modified; nothing to commit." when I try to 'Commit' from the SVN 'Status' window. I'm fully up to date with the app (cutting edge) and the svn repository. And yes, I do have the top level folder of the project selected when I run the 'Status' command.
In my case the problem was that the root directory of the TextMate project was not under svn control, just the folders underneath it. A fix in the svn bundle (using a different $Work_Path dir in the script) would likely cause it to break under other circumstances.
Gerd
On Aug 3, 2006, at 10:47 PM, Michael Larocque wrote:
On Jul 25, 2006, Gerd wrote:
On Jul 24, 2006, at 6:14 PM, Brad Choate wrote:
The second one sounds as if you have a file or files selected in the project drawer that have no local changes.
They do, svn on the command line, or using the svn bundle with one of the changed files selected in TM works fine. It is just the "Subversion Status" panel from which it doesn't work.
Gerd
Has this been fixed/addressed yet? I've checked the archives but I can't seem to find a resolution. I'm still getting the "File(s) not modified; nothing to commit." when I try to 'Commit' from the SVN 'Status' window. I'm fully up to date with the app (cutting edge) and the svn repository. And yes, I do have the top level folder of the project selected when I run the 'Status' command.
Carpe viam, Mike
Unfortunately, i'm in the final throws of launching a major new webapp. So, i don't have the time to get on it now. I feel terrible making a mess and walking away.
I really don't know what could be causing that. Or if it was any of my changes that messed it up. You might want to try reverting the bundle to an older copy, before all the crazy ajax-esque stuff. If that doesn't fix it then i probly can't help :(
thomas Aylott—subtleGradient
-
Allan Odgaard -
Chris Thomas -
Gerd Knops -
Michael Larocque -
thomas Aylott