From: Alexey Nezhdanov <snake@penza-gsm.ru>
To: git@vger.kernel.org
Subject: [offtopic]Re: "git cvsimport" with branches?
Date: Sun, 17 Jul 2005 22:02:48 +0400 [thread overview]
Message-ID: <200507172202.48642.snake@penza-gsm.ru> (raw)
In-Reply-To: <200507171633.17667.snake@penza-gsm.ru>
Sorry for noise again.
I have found two bugs in cvsps that results in the wrong import to git.
I tried to contact developer but it seems that his mail have no mailserver
ATM. Since he has made some changes for git already - probably someone on
this list have his new contact. Please tell me it or forward my mail to him.
Thanks.
For the curious, here are the bugs:
1) some branches fork off too late - cvsps shifts brahches starts forward to
the future
Example:
http://www.penza-gsm.ru/snake/testscript
2) some branches are not detected at all, not recorded as patchsets and
consequently not imported into git.
Example (branch "old"):
http://www.penza-gsm.ru/snake/simplexml.py,v
--
Respectfully
Alexey Nezhdanov
prev parent reply other threads:[~2005-07-17 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 8:40 "git cvsimport" with branches? Wolfgang Denk
2005-07-17 8:57 ` Alexey Nezhdanov
2005-07-17 9:37 ` Matthias Urlichs
2005-07-17 10:15 ` Wolfgang Denk
2005-07-17 10:48 ` Alexey Nezhdanov
2005-07-17 12:33 ` Alexey Nezhdanov
2005-07-17 18:02 ` Alexey Nezhdanov [this message]
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=200507172202.48642.snake@penza-gsm.ru \
--to=snake@penza-gsm.ru \
--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