From: merlyn@stonehenge.com (Randal L. Schwartz)
To: <git@vger.kernel.org>
Subject: git-cvsimport "you may need to merge manually"
Date: 16 Mar 2006 18:37:39 -0800 [thread overview]
Message-ID: <86veud23v0.fsf@blue.stonehenge.com> (raw)
Starting recently, git-cvsimport has always ended with "you
may need to merge manually". Why? It worked before. What
is it doing now?
$ cd /home/merlyn/Git/stonehenge.git || exit 1
$ git-cvsimport -v -k -o master -d /web/cvs stonehenge
.
.
.
skip patchset 323: 1142297290 before 1142351976
Fetching htdocs/courses.html v 1.4
Update htdocs/courses.html: 8767 bytes
Fetching htdocs/rates.html v 1.2
Update htdocs/rates.html: 2043 bytes
Tree ID 38280334da5eaa4fd80fe1011e63db4b527f1d13
Parent ID e93de754181fe963b8623423f509540021caead0
Committed patch 324 (master 2006-03-16 18:14:31)
Commit ID 985ca72d4e8a07d4189794231f035bac63c9e91d
DONE; you may need to merge manually.
$ git-status
#
# Updated but not checked in:
# (will commit)
#
# modified: htdocs/courses.html
# modified: htdocs/rates.html
#
Right... why didn't it commit those? I'm having to issue "fake"
commits now, so I've lost the cvs-log comments that were formerly
very complete and cool.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next reply other threads:[~2006-03-17 2:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 2:37 Randal L. Schwartz [this message]
2006-03-17 2:43 ` git-cvsimport "you may need to merge manually" Junio C Hamano
2006-03-17 2:57 ` Randal L. Schwartz
2006-03-17 3:04 ` Randal L. Schwartz
2006-03-17 3:23 ` Junio C Hamano
2006-03-17 3:41 ` Randal L. Schwartz
2006-03-17 4:16 ` Junio C Hamano
2006-03-17 4:19 ` Randal L. Schwartz
2006-03-18 23:21 ` Junio C Hamano
2006-03-17 7:26 ` smurf
2006-03-17 8:08 ` Junio C Hamano
2006-03-17 6:46 ` smurf
2006-03-17 8:06 ` Junio C Hamano
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=86veud23v0.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.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