From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Romain Merland" <merlorom@yahoo.fr>,
"Miguel Torroja" <miguel.torroja@gmail.com>,
"Lars Schneider" <larsxschneider@gmail.com>,
"George Vanburgh" <gvanburgh@bloomberg.net>,
"Luke Diamand" <luke@diamand.org>
Subject: [PATCH 0/1] git-p4: unshelving: fix problem with newer P4
Date: Tue, 22 May 2018 09:41:08 +0100 [thread overview]
Message-ID: <20180522084109.29787-1-luke@diamand.org> (raw)
This fixes a problem found by SZEDER Gábor with newer versions of
the Perforce database engine (2016 onwards). It looks like the
behaviour has change subtly when reporting the revision of newly
added files. The fix is to just use the file status.
Luke Diamand (1):
git-p4: unshelve: use action==add instead of rev==none
git-p4.py | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
--
2.17.0.392.gdeb1a6e9b7
next reply other threads:[~2018-05-22 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 8:41 Luke Diamand [this message]
2018-05-22 8:41 ` [PATCH 1/1] git-p4: unshelve: use action==add instead of rev==none Luke Diamand
2018-05-22 10:15 ` SZEDER Gábor
2018-05-22 13:02 ` Luke Diamand
2018-05-23 2:05 ` Junio C Hamano
2018-05-23 7:21 ` [PATCHv5 0/1] git-p4: unshelve: fix problem with newer p4d Luke Diamand
2018-05-23 7:21 ` [PATCHv5 1/1] git-p4: add unshelve command Luke Diamand
2018-05-23 16:41 ` [PATCH 1/1] git-p4: unshelve: use action==add instead of rev==none Mazo, Andrey
2018-05-23 19:12 ` Luke Diamand
2018-05-23 19:38 ` Mazo, Andrey
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=20180522084109.29787-1-luke@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gvanburgh@bloomberg.net \
--cc=larsxschneider@gmail.com \
--cc=merlorom@yahoo.fr \
--cc=miguel.torroja@gmail.com \
--cc=szeder.dev@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).