From: David Mansfield <david@cobite.com>
To: git@vger.kernel.org
Subject: [PATCH] cvsps/cvsimport: fix branch point calculation and broken branch imports
Date: Tue, 01 Apr 2008 21:34:51 -0400 [thread overview]
Message-ID: <1207100091.10532.64.camel@gandalf.cobite.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
Hi Everyone,
This email addresses a long-standing bug with the cvsimport which is due
to a bugs in cvsps. The bug is that branches can be forked off too
late.
In case you're wondering, I'm actually the original author of cvsps,
which is behind the scenes for cvsimport. I don't call myself
maintainer because I've hardly been that over the last few years.
Anyway, the fix to cvsps is attached (1st 2 patches) as well as the
patch to git-cvsimport.perl (2nd 2 patches) against the master branch as
of today's git repo.
The cvsps patches apply with fuzz against the 2.1 version which is out
there.
The full tarball of the latest cvsps version including this is available
on the website http://www.cobite.com/cvsps as well, the version is
2.2b1.
I plan to find time in the next week or so to merge all of the
outstanding patches from Yann Dirson's git repo, publish cvsps via a git
repo myself, and fix other bugs as time permits (including adding
support for multiple tags).
I'd mainly like feedback if anyone can test this.
Also, as I'm actually a newb. to this list, if I'm violating any rules,
such as how to post the patches, let me know.
Thanks,
David
P.S Also, as many people may have imported broken branches already, can
anyone thing of a way to fix the branch, (maybe with git-rebase or
something)? The breakage affects, I believe, files not ever modified on
the branch until any given point in time on the branch...
[-- Attachment #2: 01-cvsps-add-branch-object.patch --]
[-- Type: application/mbox, Size: 3429 bytes --]
[-- Attachment #3: 02-cvsps-implement-branch-point-detection.patch --]
[-- Type: application/mbox, Size: 3100 bytes --]
[-- Attachment #4: 03-cvsimport-parse-new-cvsps-output.patch --]
[-- Type: application/mbox, Size: 1252 bytes --]
[-- Attachment #5: 04-cvsimport-redo-branch-creation-process.patch --]
[-- Type: application/mbox, Size: 4260 bytes --]
next reply other threads:[~2008-04-02 1:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 1:34 David Mansfield [this message]
2008-04-02 19:29 ` [PATCH] cvsps/cvsimport: fix branch point calculation and broken branch imports Junio C Hamano
2008-04-03 1:44 ` David Mansfield
2008-04-03 2:06 ` Junio C Hamano
2008-04-03 2:27 ` David Mansfield
2008-04-03 5:47 ` Steffen Prohaska
2008-04-03 13:49 ` David Mansfield
2008-04-04 9:52 ` Michael Haggerty
2008-04-07 17:54 ` David Mansfield
2008-04-07 18:07 ` Jean-François Veillette
2008-04-09 1:53 ` Michael Haggerty
2008-04-27 5:06 ` Ping Yin
2008-04-27 5:47 ` Michael Haggerty
2008-04-27 5:51 ` Ping Yin
2008-04-27 7:38 ` Ping Yin
2008-04-27 7:43 ` Ping Yin
2008-04-27 7:48 ` Ping Yin
2008-04-27 8:48 ` Ping Yin
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=1207100091.10532.64.camel@gandalf.cobite.com \
--to=david@cobite.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).