From: David Brown <git@davidb.org>
To: Sam Vilain <sam@vilain.net>
Cc: Reece Dunn <msclrhd@googlemail.com>, Git <git@vger.kernel.org>
Subject: Re: State of Perforce importing.
Date: Tue, 18 Sep 2007 17:26:17 -0700 [thread overview]
Message-ID: <20070919002617.GA22187@old.davidb.org> (raw)
In-Reply-To: <46F06B5C.2050207@vilain.net>
On Wed, Sep 19, 2007 at 12:20:44PM +1200, Sam Vilain wrote:
>If you can get a hold of the "checkpoint" and "journal" files, you could
>probably throw the client spec data into a few Pg tables, chuck a couple
>of constraints on it to confirm that it works the way you thought, and
>then get the information on what's where using a SQL query. The file
>images themselves can come from wherever, it doesn't really matter
>because there are MD5 hashes in the data tables you can use to confirm
>you got the right file.
In my instance, I don't have an account on the P4 server, so I'm going to
have to deal with this through P4's normal client.
I don't have much confidence that P4 really knows what it is doing when it
comes to integrate, so I'm not much worried about branches. But, I do want
to accurately get the history of a particular branch.
So far, the only thing that isn't working is the execute bit doesn't get
set on files that should have it.
Dave
next prev parent reply other threads:[~2007-09-19 0:26 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 [this message]
2007-09-19 0:23 ` Sam Vilain
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=20070919002617.GA22187@old.davidb.org \
--to=git@davidb.org \
--cc=git@vger.kernel.org \
--cc=msclrhd@googlemail.com \
--cc=sam@vilain.net \
/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).