Re: inconsistent logs when displayed on screen / piped to a file

2012-07-31 Thread Jan Engelhardt
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... -- To unsubscribe f

Re: inconsistent logs when displayed on screen / piped to a file

2012-07-30 Thread Mojca Miklavec
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 --d

Re: inconsistent logs when displayed on screen / piped to a file

2012-07-30 Thread Carlos Martín Nieto
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

Re: inconsistent logs when displayed on screen / piped to a file

2012-07-30 Thread Michael J Gruber
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

inconsistent logs when displayed on screen / piped to a file

2012-07-30 Thread Mojca Miklavec
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, ru