git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* inconsistent logs when displayed on screen / piped to a file
@ 2012-07-30 12:25 Mojca Miklavec
  2012-07-30 13:39 ` Michael J Gruber
  0 siblings, 1 reply; 5+ messages in thread
From: Mojca Miklavec @ 2012-07-30 12:25 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: inconsistent logs when displayed on screen / piped to a file
  2012-07-30 12:25 inconsistent logs when displayed on screen / piped to a file Mojca Miklavec
@ 2012-07-30 13:39 ` Michael J Gruber
  2012-07-30 13:50   ` Carlos Martín Nieto
  2012-07-30 14:58   ` Mojca Miklavec
  0 siblings, 2 replies; 5+ messages in thread
From: Michael J Gruber @ 2012-07-30 13:39 UTC (permalink / raw)
  To: Mojca Miklavec; +Cc: git

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: inconsistent logs when displayed on screen / piped to a file
  2012-07-30 13:39 ` Michael J Gruber
@ 2012-07-30 13:50   ` Carlos Martín Nieto
  2012-07-30 14:58   ` Mojca Miklavec
  1 sibling, 0 replies; 5+ messages in thread
From: Carlos Martín Nieto @ 2012-07-30 13:50 UTC (permalink / raw)
  To: Michael J Gruber; +Cc: Mojca Miklavec, git

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: inconsistent logs when displayed on screen / piped to a file
  2012-07-30 13:39 ` Michael J Gruber
  2012-07-30 13:50   ` Carlos Martín Nieto
@ 2012-07-30 14:58   ` Mojca Miklavec
  2012-07-31  8:08     ` Jan Engelhardt
  1 sibling, 1 reply; 5+ messages in thread
From: Mojca Miklavec @ 2012-07-30 14:58 UTC (permalink / raw)
  To: Michael J Gruber; +Cc: git

On Mon, Jul 30, 2012 at 3:39 PM, Michael J Gruber wrote:
> Mojca Miklavec venit, vidit, dixit 30.07.2012 14:25:
>>
>> 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: inconsistent logs when displayed on screen / piped to a file
  2012-07-30 14:58   ` Mojca Miklavec
@ 2012-07-31  8:08     ` Jan Engelhardt
  0 siblings, 0 replies; 5+ messages in thread
From: Jan Engelhardt @ 2012-07-31  8:08 UTC (permalink / raw)
  To: Mojca Miklavec; +Cc: Michael J Gruber, git

On Monday 2012-07-30 16:58, Mojca Miklavec wrote:
>>
>> COLUMNS=YourNumber git log YourArgs > YourFile
>
>Wow, perfect, thank you very much. Setting COLUMNS=200 (the high
>number just in case) solved the problem.

200 ought to be enough for everybody? PATH_MAX is never enough...

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2012-07-31  8:09 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-30 12:25 inconsistent logs when displayed on screen / piped to a file Mojca Miklavec
2012-07-30 13:39 ` Michael J Gruber
2012-07-30 13:50   ` Carlos Martín Nieto
2012-07-30 14:58   ` Mojca Miklavec
2012-07-31  8:08     ` Jan Engelhardt

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).