From: Marko Macek <Marko.Macek@gmx.net>
To: Michael Haggerty <mhagger@alum.mit.edu>,
git@vger.kernel.org, users@cvs2svn.tigris.org,
prohaska@zib.de
Subject: Re: cvs2svn conversion directly to git ready for experimentation
Date: Thu, 02 Aug 2007 21:22:31 +0200 [thread overview]
Message-ID: <46B22EF7.80108@gmx.net> (raw)
In-Reply-To: <46B2132D.7090304@alum.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
Michael Haggerty wrote:
> This can definitely be caused by unlabeled branches. It can also be
> caused by branches rooted in a vendor branch. In many cases, such
> branches can actually be grafted onto trunk, but cvs2svn does not (yet)
> attempt this.
It would be nice to be able to exclude the vendor branch if only
the initial commit was made on it (or maybe handle it better, by
remapping the commits to the main branch when they match).
I have tested this on my repository and currently gitk draws
large 'railroad switching stations' because many tags have the
vendor branch as a parent (and in some cases also the parent branch,
in addition to the parent commit).
Mark
[-- Attachment #2: railroad.png --]
[-- Type: image/png, Size: 3828 bytes --]
[-- Attachment #3: Type: text/plain, Size: 193 bytes --]
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cvs2svn.tigris.org
For additional commands, e-mail: users-help@cvs2svn.tigris.org
next prev parent reply other threads:[~2007-08-02 19:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 0:09 cvs2svn conversion directly to git ready for experimentation Michael Haggerty
2007-08-01 0:41 ` Johannes Schindelin
2007-08-01 22:09 ` Jakub Narebski
2007-08-02 16:58 ` Michael Haggerty
2007-08-02 23:44 ` Jon Smirl
2007-08-02 8:49 ` Steffen Prohaska
2007-08-02 17:23 ` Michael Haggerty
2007-08-02 19:22 ` Marko Macek [this message]
2007-08-02 23:59 ` Jon Smirl
2007-08-05 7:58 ` Oswald Buddenhagen
2007-08-02 17:35 ` Simon 'corecode' Schubert
2007-08-02 19:13 ` Steffen Prohaska
2007-08-02 19:29 ` Simon 'corecode' Schubert
2007-08-02 20:21 ` Robin Rosenberg
[not found] ` <200708022221.13129.robin.rosenberg.lists-RgPrefM1rjDQT0dZR+AlfA@public.gmane.org>
2007-08-02 20:31 ` Lübbe Onken
2007-08-02 20:32 ` Lübbe Onken
2007-08-02 20:33 ` Lübbe Onken
2007-08-02 22:02 ` Steffen Prohaska
2007-08-02 22:50 ` Simon 'corecode' Schubert
2007-08-02 23:50 ` Michael Haggerty
2007-08-03 8:40 ` Simon 'corecode' Schubert
2007-08-04 8:28 ` Steffen Prohaska
2007-08-03 3:07 ` Shawn O. Pearce
2007-08-02 23:37 ` Michael Haggerty
2007-08-02 20:43 ` Linus Torvalds
2007-08-02 23:19 ` Michael Haggerty
2007-08-03 3:12 ` Shawn O. Pearce
2007-08-02 23:55 ` Jon Smirl
[not found] ` <8b65902a0708010438s24d16109k601b52c04cf9c066@mail.gmail.com>
2007-08-02 15:34 ` Michael Haggerty
2007-08-02 23:08 ` Martin Langhoff
2007-08-03 4:03 ` Johannes Schindelin
2007-08-03 6:48 ` Steffen Prohaska
2007-08-03 7:10 ` Steffen Prohaska
2007-08-03 8:36 ` Michael Haggerty
2007-08-03 14:35 ` Patwardhan, Rajesh
2007-08-03 15:41 ` Jon Smirl
2007-08-03 16:42 ` Patwardhan, Rajesh
2007-08-03 18:58 ` Michael Haggerty
2007-08-03 20:16 ` Jon Smirl
2007-08-03 20:27 ` Jon Smirl
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=46B22EF7.80108@gmx.net \
--to=marko.macek@gmx.net \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=prohaska@zib.de \
--cc=users@cvs2svn.tigris.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).