git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Reece Dunn <msclrhd@googlemail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: State of Perforce importing.
Date: Wed, 19 Sep 2007 12:23:43 +1200	[thread overview]
Message-ID: <46F06C0F.3040609@vilain.net> (raw)
In-Reply-To: <3f4fd2640709181053t70b7abcdi2c4eaf67e7b75338@mail.gmail.com>

Reece Dunn wrote:
> There is no need to create yet another Perforce importing tool, git-p4
> works well in most cases. If we focus on improving git-p4, extending
> it to support the functionality mentioned here, fix the issues that
> there are with it, then that will be more beneficial to the community
> as they will not have to learn another tool with a different set of
> bugs and issues.

I like my approach; it's clean and I think shows a tasteful level of
distrust towards the sanity and integrity of the data held by Perforce.
 Actually it really helped me understand what was really going on;
because the information as displayed by for instance "p4 integrate" is
a lot more confusing than the underlying tables (IMHO).

Sam.

  parent reply	other threads:[~2007-09-19  0:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 19:30 State of Perforce importing David Brown
2007-09-18  6:58 ` Simon Hausmann
2007-09-18  7:27 ` Sam Vilain
2007-09-18 15:49   ` David Brown
2007-09-18 17:53     ` Reece Dunn
2007-09-18 23:19       ` David Brown
2007-09-19  0:20         ` Sam Vilain
2007-09-19  0:26           ` David Brown
2007-09-19  0:23       ` Sam Vilain [this message]
2007-09-19 21:20         ` Reece Dunn
2007-09-20  6:12     ` Dmitry Kakurin
2007-09-18 23:37 ` David Brown
2007-09-19  0:23   ` Sam Vilain
2007-09-19  0:27     ` David Brown
2007-09-19  6:19   ` Simon Hausmann
2007-09-19 17:12     ` David Brown
2007-09-19 18:23       ` Reece Dunn
2007-09-19 18:25         ` David Brown
2007-09-19 18:56           ` Reece Dunn

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46F06C0F.3040609@vilain.net \
    --to=sam@vilain.net \
    --cc=git@vger.kernel.org \
    --cc=msclrhd@googlemail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).