From: Matt Arsenault <arsenm2@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Pete Wyckoff <pw@padd.com>,
Luke Diamand <luke@diamand.org>
Subject: Re: [PATCH] Fix git p4 sync errors
Date: Wed, 24 Oct 2012 19:41:36 -0700 [thread overview]
Message-ID: <F0F92B0A-D37F-40D4-A0DF-43EEDA2818B9@gmail.com> (raw)
In-Reply-To: <7vwqyjfxwd.fsf@alter.siamese.dyndns.org>
On Oct 21, 2012, at 12:06 , Junio C Hamano <gitster@pobox.com> wrote:
>
>>
>> This solves errors in some cases when syncing renamed files.
>
> Can you be a bit more descriptive? What are "errors in some case"?
>
It might just be when files are renamed. I ran into this after months of using it, and I'm skeptical that in that time no files were ever renamed. I'm not sure what was special about the file that was renamed. (There also might have been deleted files in the same commit, not sure if that matters)
> In short, what I am getting at are:
>
> - What breaks by not passing "-s"? What are the user visible
> symptoms?
There's a key error on the line
line 2198: epoch = details["time"]
The details object is an error different fields set (I don't remember what it is exactly, I'm not at work right now)
>
> - Why is it a bug not to pass "-s"? How does the bug happen?
I encountered this one time after using it for months. One day I couldn't git p4 rebase with the key error. I searched for the error and found some version of git-p4 that fixed a similar error by adding the -s to describe. Adding the -s fixed the error and everything seemed to be working correctly.
next prev parent reply other threads:[~2012-10-25 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 1:59 [PATCH] Fix git p4 sync errors Matt Arsenault
2012-10-21 19:06 ` Junio C Hamano
2012-10-25 2:41 ` Matt Arsenault [this message]
2012-10-26 15:44 ` Christian Couder
2012-10-28 15:06 ` Pete Wyckoff
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=F0F92B0A-D37F-40D4-A0DF-43EEDA2818B9@gmail.com \
--to=arsenm2@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luke@diamand.org \
--cc=pw@padd.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).