From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Michael Witten <mfwitten@MIT.EDU>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] git-cvsexportcommit.perl: git-apply no longer needs --binary
Date: Tue, 16 Oct 2007 23:49:17 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710162348260.25221@racer.site> (raw)
In-Reply-To: <561D7B44-9EDE-447B-A751-BE6E3A3AD9CC@mit.edu>
Hi,
On Tue, 16 Oct 2007, Michael Witten wrote:
> On 16 Oct 2007, at 5:20:14 PM, Robin Rosenberg wrote:
>
> > So all this series does is... making it harder to follow the history?
>
> If you follow the history solely on patches.
>
>
> > Ack for removing the --binary, the rest is just noise
>
> I think fixing the tabs is more important than removing --binary.
>
> It's clear the the entropy of tabulation increases over time;
> the tab patch acts as a buffer to reconstruct a clean signal.
Git. The most advanced TCM - Tab Code Manager. It's not about source,
it's about tabs.
;-)
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-16 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 8:08 [PATCH 1/3] git-cvsexportcommit.perl tabified Michael Witten
2007-10-16 8:08 ` [PATCH 2/3] git-cvsexportcommit.perl tmpdir removed Michael Witten
2007-10-16 8:08 ` [PATCH 3/3] git-cvsexportcommit.perl: git-apply no longer needs --binary Michael Witten
2007-10-16 13:04 ` Johannes Schindelin
2007-10-16 15:27 ` Michael Witten
2007-10-16 21:20 ` Robin Rosenberg
2007-10-16 22:13 ` Michael Witten
2007-10-16 22:49 ` Johannes Schindelin [this message]
2007-10-16 23:22 ` Michael Witten
2007-10-17 1:11 ` Shawn O. Pearce
2007-10-17 1:34 ` Michael Witten
2007-10-20 13:59 ` Robin Rosenberg
2007-10-17 2:25 ` [PATCH 2/3] git-cvsexportcommit.perl tmpdir removed Shawn O. Pearce
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=Pine.LNX.4.64.0710162348260.25221@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mfwitten@MIT.EDU \
--cc=robin.rosenberg.lists@dewire.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).