From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Barak A. Pearlmutter" <barak@cs.nuim.ie>
Cc: git@vger.kernel.org
Subject: Re: git-cvsexportcommit keyword mismatch issue
Date: Wed, 16 Jul 2008 12:31:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807161229460.8503@eeepc-johanness> (raw)
In-Reply-To: <E1KJ30U-0004EL-BV@corti>
Hi,
On Wed, 16 Jul 2008, Barak A. Pearlmutter wrote:
> So what I'm hoping is that this lengthy discourse of mine will convince
> someone to add code to git-cvsexportcommit that causes the patch
> creation and application stuff inside it to ignore keyword expansion
> mismatches (on files which do not have -kb on in CVS), perhaps by simply
> contracting keywords on all files/patches from both CVS/git at an early
> stage.
I doubt that this is going to happen. Obviously, it has been nonbody's
itch _enough_ to scratch it.
I see your problem, but unless you start hacking, I do not see it being
solved anytime soon.
Ciao,
Dscho
next prev parent reply other threads:[~2008-07-16 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 9:09 git-cvsexportcommit keyword mismatch issue Barak A. Pearlmutter
2008-07-16 10:31 ` Johannes Schindelin [this message]
2008-07-16 23:16 ` Lars Noschinski
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.00.0807161229460.8503@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=barak@cs.nuim.ie \
--cc=git@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox