From: Alex Bennee <kernel-hacker@bennee.com>
To: git@vger.kernel.org
Subject: [PATCH] Make git-cvsexportcommit "status" each file in turn
Date: Wed, 15 Aug 2007 14:27:28 +0100 [thread overview]
Message-ID: <1187184448.13096.54.camel@murta.transitives.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
Hi,
It turns out CVS doesn't always give the status output in the order
requested. According to my local CVS gurus this is a known CVS issue.
The attached patch just makes the script check each file in turn. It's
slower but correct.
I also slightly formatted the warn output when it detects problems as
multiple line wraps with long file paths where making my eyes bleed :-)
--
Alex, homepage: http://www.bennee.com/~alex/
Absence makes the heart go wander.
[-- Attachment #2: 0001-Make-git-cvsexportcommit-status-each-CVS-file-in-tur.patch --]
[-- Type: application/mbox, Size: 2275 bytes --]
next reply other threads:[~2007-08-15 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 13:27 Alex Bennee [this message]
2007-08-15 14:04 ` [PATCH] Make git-cvsexportcommit "status" each file in turn Peter Baumann
2007-08-15 16:25 ` Alex Bennee
2007-08-15 19:40 ` Robin Rosenberg
2007-08-15 15:47 ` Alex Bennee
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=1187184448.13096.54.camel@murta.transitives.com \
--to=kernel-hacker@bennee.com \
--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;
as well as URLs for NNTP newsgroup(s).