From: Michael J Gruber <git@drmicha.warpmail.net>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: inconsistent logs when displayed on screen / piped to a file
Date: Mon, 30 Jul 2012 15:39:31 +0200 [thread overview]
Message-ID: <50168E93.2090202@drmicha.warpmail.net> (raw)
In-Reply-To: <CALBOmsYh5AgpRQe28yUcChqemQ7HFMHahesGj_MPwQXDF-EM=Q@mail.gmail.com>
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
next prev parent reply other threads:[~2012-07-30 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2012-07-30 13:50 ` Carlos Martín Nieto
2012-07-30 14:58 ` Mojca Miklavec
2012-07-31 8:08 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50168E93.2090202@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=mojca.miklavec.lists@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).