From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: git@vger.kernel.org
Subject: Warning: cvsexportcommit considered dangerous
Date: Sun, 4 Nov 2007 16:41:12 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711041638270.4362@racer.site> (raw)
Hi,
ever since the up-to-date check was changed to use just one call to "cvs
status", a bug was present. Now cvsexportcommit expects "cvs status" to
return the results in the same order as the file names were passed.
This is not true, as I had to realise with one of my projects on
sourceforge.
Since time is so scarce on my side, I will not have time to fix this bug,
but will instead return to my old "commit by hand" procedure.
Ciao,
Dscho
next reply other threads:[~2007-11-04 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 16:41 Johannes Schindelin [this message]
2007-11-04 18:16 ` Warning: cvsexportcommit considered dangerous Steffen Prohaska
2007-11-04 21:35 ` Johannes Schindelin
2007-11-04 23:05 ` Robin Rosenberg
2007-11-04 23:46 ` Johannes Schindelin
2007-11-15 11:59 ` 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=Pine.LNX.4.64.0711041638270.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--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).