Skip to content
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

[Question] How to save the report generated during a commit #6

Closed
crile opened this issue Jun 27, 2016 · 10 comments
Closed

[Question] How to save the report generated during a commit #6

crile opened this issue Jun 27, 2016 · 10 comments
Assignees

Comments

@crile
Copy link

crile commented Jun 27, 2016

Hello, thanks for this good software.

Maybe I use it poorly, but I want to save the report generated during the commit.
For example

Added: test_1.txt
Added: test_2.txt
Content modified: test_3.txt

It seems that, the log command doesn't return it. Only this message appears:
2 added, 1 content modified

My actual poor wordaround: Run the commit command one time, get the report, cancel the commit, run the commit again with the comment filled with the report.

@evrignaud
Copy link
Owner

Hi,
I'm not sure to understand your use case, but I think you should consider using the diff command which produce exactly the output you want.
Regards,
/Etienne

@crile
Copy link
Author

crile commented Jun 29, 2016

Thank for your answer, I will try to explain again with an example.

I have one directory with one file (1.txt).
I run fim with init command and then a commit.
The output of the log command should be:

State #1 [..]
Comment: blabla
1 added

I add one file (2.txt). I commit again.
The output of the log command should be:

State #1 [..]
Comment: blabla
1 added
State #2 [..]
Comment: blabla
1 added

I modify the file 1.txt and add a file (3.txt). Then commit.
The output of the log command should be:

State #1 [..]
Comment: blabla
1 added
State #2 [..]
Comment: blabla
1 added
State #3 [..]
Comment: blabla
1 added
1 modified

How can I know that during the state 2 the added file is 2.txt for example ?
How can I know that during the state 3 the moddified file is 1.txt ?

I see these informations when I commit but with the log command, I can't.

@evrignaud
Copy link
Owner

Ok, I understand. You are right, it's possible for the log command to display all this details, because each file entry have a modification field with a detailed reason. I'll manage to add this in the next version.
Stay tuned to try it in a Fim snapshot.

@crile
Copy link
Author

crile commented Jul 1, 2016

Great, thanks.

@evrignaud
Copy link
Owner

Hi Cyril,

I have fixed the issue.
The 'fim log' command now display the same output as the 'fim commit' or 'fim diff' commands.
The repository format have not changed, but more information are saved during commit.
The consequence is that 'fim log' output work 100% with new commits. And with old ones it works but some information are missing.
Are you able to build a Snapshot of Fim and try what is on the master in order to check if what I did is what you expected?
Regards,
/Etienne

@crile
Copy link
Author

crile commented Oct 3, 2016

Sorry for the late answer, I don't have too much time right know. I will try it later.

@evrignaud
Copy link
Owner

I'm going to build a release soon, so I close this issue.
This way you will be able to test this new feature.
Don't hesitate to tell me if something can be adjusted.

@evrignaud evrignaud self-assigned this Oct 8, 2016
@crile
Copy link
Author

crile commented Oct 14, 2016

I am not a developer but when I try to build it, it fails.
So I try your last release v1.2.1.
It works.
Thanks.

@evrignaud
Copy link
Owner

Great. Is it working as you expected?

@crile
Copy link
Author

crile commented Oct 14, 2016

Yes thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants