Hello,
I'm trying to use "git log" to generate ChangeLog for a project
recently migrated from CVS.
The problem is that
git log --summary --stat --no-merges --date=short --decorate=short
behaves differently when the result is displayed on screen and when it
is piped to a file.
For example, running the commands:
a) git log --summary --stat --no-merges --date=short
--decorate=short e9f65aa976
b) git log --summary --stat --no-merges --date=short
--decorate=short e9f65aa976 > /tmp/log.txt
would result in two different outputs:
a)
aquaterm/Docs/gptProtocol.rtf | 316
++++++++++++++++++++++++++
aquaterm/English.lproj/GPTInfoWindow.nib/classes.nib | 12 +
aquaterm/English.lproj/GPTInfoWindow.nib/info.nib | 12 +
aquaterm/English.lproj/GPTInfoWindow.nib/objects.nib | Bin 0 -> 1010 bytes
aquaterm/English.lproj/GPTInfoWindow~.nib/classes.nib | 4 +
aquaterm/English.lproj/GPTInfoWindow~.nib/info.nib | 12 +
aquaterm/English.lproj/GPTInfoWindow~.nib/objects.nib | Bin 0 -> 1232 bytes
aquaterm/English.lproj/GPTWindow.nib/classes.nib | 13 ++
aquaterm/English.lproj/GPTWindow.nib/info.nib | 12 +
b)
aquaterm/Docs/gptProtocol.rtf | 316 ++++++
.../English.lproj/GPTInfoWindow.nib/classes.nib | 12 +
aquaterm/English.lproj/GPTInfoWindow.nib/info.nib | 12 +
.../English.lproj/GPTInfoWindow.nib/objects.nib | Bin 0 -> 1010 bytes
.../English.lproj/GPTInfoWindow~.nib/classes.nib | 4 +
aquaterm/English.lproj/GPTInfoWindow~.nib/info.nib | 12 +
.../English.lproj/GPTInfoWindow~.nib/objects.nib | Bin 0 -> 1232 bytes
aquaterm/English.lproj/GPTWindow.nib/classes.nib | 13 +
aquaterm/English.lproj/GPTWindow.nib/info.nib | 12 +
The project where the results could be easily reproduced is the following:
https://github.com/AquaTerm/AquaTerm
git://github.com/AquaTerm/AquaTerm.git
It is possible that I screwed up something when importing the project
from CVS. In that case I would be happy if someone could point me out
what exactly I did wrong, and I can still rewrite the history before
the first release of the project using git.
But in any case I find it weird that I get two different outputs.
I would be grateful for any clues or hints about what goes wrong.
Mojca
From: Michael J Gruber <hidden> Date: 2016-06-15 22:54:22
Mojca Miklavec venit, vidit, dixit 30.07.2012 14:25:
Hello,
I'm trying to use "git log" to generate ChangeLog for a project
recently migrated from CVS.
The problem is that
git log --summary --stat --no-merges --date=short --decorate=short
behaves differently when the result is displayed on screen and when it
is piped to a file.
For example, running the commands:
a) git log --summary --stat --no-merges --date=short
--decorate=short e9f65aa976
b) git log --summary --stat --no-merges --date=short
--decorate=short e9f65aa976 > /tmp/log.txt
would result in two different outputs:
a)
aquaterm/Docs/gptProtocol.rtf | 316
++++++++++++++++++++++++++
aquaterm/English.lproj/GPTInfoWindow.nib/classes.nib | 12 +
aquaterm/English.lproj/GPTInfoWindow.nib/info.nib | 12 +
aquaterm/English.lproj/GPTInfoWindow.nib/objects.nib | Bin 0 -> 1010 bytes
aquaterm/English.lproj/GPTInfoWindow~.nib/classes.nib | 4 +
aquaterm/English.lproj/GPTInfoWindow~.nib/info.nib | 12 +
aquaterm/English.lproj/GPTInfoWindow~.nib/objects.nib | Bin 0 -> 1232 bytes
aquaterm/English.lproj/GPTWindow.nib/classes.nib | 13 ++
aquaterm/English.lproj/GPTWindow.nib/info.nib | 12 +
b)
aquaterm/Docs/gptProtocol.rtf | 316 ++++++
.../English.lproj/GPTInfoWindow.nib/classes.nib | 12 +
aquaterm/English.lproj/GPTInfoWindow.nib/info.nib | 12 +
.../English.lproj/GPTInfoWindow.nib/objects.nib | Bin 0 -> 1010 bytes
.../English.lproj/GPTInfoWindow~.nib/classes.nib | 4 +
aquaterm/English.lproj/GPTInfoWindow~.nib/info.nib | 12 +
.../English.lproj/GPTInfoWindow~.nib/objects.nib | Bin 0 -> 1232 bytes
aquaterm/English.lproj/GPTWindow.nib/classes.nib | 13 +
aquaterm/English.lproj/GPTWindow.nib/info.nib | 12 +
The project where the results could be easily reproduced is the following:
https://github.com/AquaTerm/AquaTerm
git://github.com/AquaTerm/AquaTerm.git
It is possible that I screwed up something when importing the project
from CVS. In that case I would be happy if someone could point me out
what exactly I did wrong, and I can still rewrite the history before
the first release of the project using git.
But in any case I find it weird that I get two different outputs.
I would be grateful for any clues or hints about what goes wrong.
Mojca
The only difference that I see is the formatting. ("..." is merely an
abbreviation for a leading path.)
a) probes your terminal for the number of columns and uses all available
space.
b) goes to a file and has no connected terminal, thus uses a default
column number. You can change that number using
COLUMNS=YourNumber git log YourArgs > YourFile
Michael
From: Carlos Martín Nieto <hidden> Date: 2016-06-15 22:54:22
On Mon, 2012-07-30 at 15:39 +0200, Michael J Gruber wrote:
a) probes your terminal for the number of columns and uses all available
space.
b) goes to a file and has no connected terminal, thus uses a default
column number. You can change that number using
COLUMNS=YourNumber git log YourArgs > YourFile
You can also pass a width to --stat. See the git log manpage for details
about which widths you can override.
cmn
On Mon, Jul 30, 2012 at 3:39 PM, Michael J Gruber wrote:
Mojca Miklavec venit, vidit, dixit 30.07.2012 14:25:
quoted
I'm trying to use "git log" to generate ChangeLog for a project
recently migrated from CVS.
The problem is that
git log --summary --stat --no-merges --date=short --decorate=short
behaves differently when the result is displayed on screen and when it
is piped to a file.
The only difference that I see is the formatting. ("..." is merely an
abbreviation for a leading path.)
a) probes your terminal for the number of columns and uses all available
space.
b) goes to a file and has no connected terminal, thus uses a default
column number. You can change that number using
COLUMNS=YourNumber git log YourArgs > YourFile
Wow, perfect, thank you very much. Setting COLUMNS=200 (the high
number just in case) solved the problem.
Mojca