-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modified files get not recognized #20
Comments
I have a similar problem but with other solution. (I am Russian, but it does not matter)
|
Hello, thanks for your help. That did the trick. I append here a diff for those who can put it upstream.
|
Can confirm. This also resolves an issue with globs not working in nested directories. |
This is likely a consequence of my ignorance to git porcelain, where output would be less subject to change and hence more amenable to parsing. If I ever get time to work on this repo in earnest, I would drop the custom output processing altogether anyway. I'll make this change and cut a new release. |
OK, cut 0.27.1 if all/any of you want to grab, test, and then feel free to close this issue. |
Pulled and tested this evening. Works as advertised. Thanks, Thomas!
|
Hello,
I just tried flashbake using my ubuntu 14.04LTS. The effect was - well - catastrophic. Flashbake did not recognize any modifications of any file. Thus I installed the most recent version from github but without success.
A bit more verbose:
git init
).flashbake
on the directory. The file gets checked in (ok so far).flashbake
it gets checked in.git status
shows the modifications clearly. When I applyflashbreak
I get the message that no constent to be checked in has changed. (???)Please note a small "bug": You seem to parse the output of git in some sense. If the user has a different language than English, you get into trouble. In this case (I am German) flashbreak did not even check in the very first version. I had to manually
export LANG=C
before. Maybe you might alter the LANG environment variable on calling git such that English is always used.Hope this helps.
Christian Wolf
The text was updated successfully, but these errors were encountered: