From: Michael Horowitz <michael.horowitz@ieee.org>
To: Tor Arvid Lund <torarvid@gmail.com>
Cc: Pete Wyckoff <pw@padd.com>, git@vger.kernel.org
Subject: Re: git-p4 issue
Date: Fri, 15 Apr 2011 16:39:54 -0400 [thread overview]
Message-ID: <BANLkTikDDDtyJB992DFNtvgMrGvbWf=rMw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimmVQAcx7hiQFUBcoAGdvPhktPuMg@mail.gmail.com>
I am sure that is a common mistake people make, but not in this case.
I have been using it successfully for a while now, it just suddenly
stopped working, not sure what changed. I am not seeing anything on
remotes/p4/master either, and I was originally doing rebase and went
back to sync so I could run "--verbose" and see if it was even
downloading those changes. I can clearly see it says it is
downloading them, but then they just don't end up in git.
Since I don't see an error message about it failing to sync, I am at a
loss to figure out why it says it succeeded, but it didn't. Could
there be one step in the code that is not catching an error condition?
I am not all that familiar with Python, but if someone could point me
where to put some debug messages, I can do some testing.
Thanks,
Mike
On Fri, Apr 15, 2011 at 4:22 PM, Tor Arvid Lund <torarvid@gmail.com> wrote:
>
> On Fri, Apr 15, 2011 at 5:00 AM, Michael Horowitz
> <michael.horowitz@ieee.org> wrote:
> > Pete,
> >
> > I was hoping you could help me out again. After using git-p4 for a
> > while without a problem, it has suddenly stopped working for me. I am
> > using the latest master. I haven't seen any recent changes that I
> > think could have caused this, but maybe you'll have some insight.
> >
> > The issue is that when I do a git-p4 sync on my existing repository,
> > it reports success, but seems to do nothing. It does not download the
> > latest changes from p4. If I delete my repository and start over, it
> > will download all the latest changes, even the ones it was not
> > downloading previously, but if I try to sync again later, it does not
> > do anything. I tried running it with the "--verbose" mode, and I see
> > it says it is loading each of the changes, but they are not ending up
> > in the git repository, and it is not reporting any errors.
>
> Hi, Michael.
>
> Is it possible that you expect that 'git p4 sync' should update your
> working branch and/or working tree? Assuming a simple clone with a
> local master branch, running 'git-p4 sync' will update the branch
> remotes/p4/master, but it won't do anything on my working master
> branch...
>
> Maybe you want to call 'git rebase p4/master' afterwards, or use the
> shorthand 'git p4 rebase' to do a sync+rebase.
>
> Regards,
> Tor Arvid.
>
> > Any ideas of what this could be? Is there anything else I can run to
> > help debug this?
> >
> > Thanks,
> >
> > Mike
> > --
> > To unsubscribe from this list: send the line "unsubscribe git" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
next prev parent reply other threads:[~2011-04-15 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 3:00 git-p4 issue Michael Horowitz
2011-04-15 20:22 ` Tor Arvid Lund
2011-04-15 20:39 ` Michael Horowitz [this message]
2011-04-16 16:01 ` Pete Wyckoff
2011-04-18 12:59 ` Vitor Antunes
2011-04-19 3:57 ` Michael Horowitz
2011-04-19 9:59 ` Vitor Antunes
2011-04-20 0:31 ` Pete Wyckoff
2011-04-20 2:40 ` Michael Horowitz
2011-04-20 10:51 ` Vitor Antunes
2011-05-06 20:16 ` Michael Horowitz
2011-05-13 14:31 ` Vitor Antunes
2011-12-17 5:52 ` Michael Horowitz
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 17:28 Brent
[not found] <AANLkTikXHJqmzZDv6NhujHqjUFva-uCRB3td306vi=WX@mail.gmail.com>
[not found] ` <AANLkTi=b60kqd6fRXzf39BBepLOeA3ts6EN3AuY0iAp4@mail.gmail.com>
2011-02-24 21:12 ` Michael Horowitz
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='BANLkTikDDDtyJB992DFNtvgMrGvbWf=rMw@mail.gmail.com' \
--to=michael.horowitz@ieee.org \
--cc=git@vger.kernel.org \
--cc=pw@padd.com \
--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).