From: Kent Borg <kentborg@borg.org>
To: Tor Arvid Lund <torarvid@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-p4
Date: Thu, 16 Sep 2010 08:14:19 -0400 [thread overview]
Message-ID: <4C920A1B.1030707@borg.org> (raw)
In-Reply-To: <AANLkTingvEFDygkKipBXfCHJr2=oMQrYv3FKpxpo+TkW@mail.gmail.com>
Tor Arvid Lund wrote:
> Well, then I think you are a bit confused ;)
>
That I know is true, but I am making progress.
- I have "git p4 rebase"-d changes from p4 world out to
git. More than once even.
- I have "git p4 submit"-ted changes from git back into
p4 world. Again, more than once.
- I can pull and push from/to this git repository to my primary git
repository.
> The p4/master branch is git's view of your p4 history. So p4/master
> points to the most recent git/perforce commit.
Yes.
> An important side point
> here, is that if you have another remote (which you do in your case)
> that is a pure git remote that knows nothing about p4, then the
> p4/master branch and the origin/master branch will be disjoint.
>
That, I think I fixed! The first commit on the p4/master branch used to
be a sync from p4, but after surgery on branch references (correct
term?) my gateway git-p4 repository's p4/master branch now has history
all the way back to the beginning of time in the git universe (back to
good ol' Linux 2.6.12-rc2). The recent commits have git-p4 comments
that mark the matching p4 changesets. I am not sure exactly how I did
it, but it seems that doing a "git-p4 rebase" instead of "git-p4 sync"
made my surgery work.
One odd thing that had me worried was seeing the git side of the gateway
repository show a single history back and then show a short split
history and then a single history, flopping as I ran transactions
through it. I am not sure what was going on, but I think git-p4 is
doing an amend of the last commit to put its notes in the message, and
if I have anything newer hanging from that commit this is a very bad
thing. I am still worried but less so as long as I behave myself about
not expecting it to make amendments to anything but the newest commits.
Part of the consideration is to simply be very aware of those "[git-p4:
..." notes and decide where this should propagate to and design the
workflow accordingly. (lkml probably won't want to see p4 notations...)
But anyway, I seem to have git-p4 working in both directions, with a
complete beginning-of-time history on the git side.
Tor Arvid: I owe you a beer (or whatever you drink when someone offers
you a beer), how often do you visit Boston?
Thanks for everyone's patience with a newbie,
-kb
next prev parent reply other threads:[~2010-09-16 12:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C8A8CE8.90600@borg.org>
2010-09-10 21:53 ` git-p4 Alejandro Riveira Fernández
2010-09-11 18:42 ` git-p4 Tor Arvid Lund
2010-09-12 15:30 ` git-p4 Kent Borg
2010-09-12 17:22 ` git-p4 Tor Arvid Lund
2010-09-12 17:59 ` git-p4 Kent Borg
2010-09-12 19:54 ` git-p4 Tor Arvid Lund
2010-09-12 20:07 ` git-p4 Kent Borg
2010-09-12 20:12 ` git-p4 Tor Arvid Lund
2010-09-13 14:23 ` git-p4 Kent Borg
2010-09-13 15:01 ` git-p4 Tor Arvid Lund
2010-09-13 16:28 ` git-p4 Kent Borg
2010-09-13 21:58 ` git-p4 Tor Arvid Lund
2010-09-16 12:14 ` Kent Borg [this message]
2010-09-16 13:54 ` git-p4 Tor Arvid Lund
2008-09-07 13:17 git-p4 dhruva
-- strict thread matches above, loose matches on Subject: below --
2008-09-07 13:17 git-p4 dhruva
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=4C920A1B.1030707@borg.org \
--to=kentborg@borg.org \
--cc=git@vger.kernel.org \
--cc=torarvid@gmail.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.
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).