From: Daniel Bingham <daniel@dbingham.com>
To: git@vger.kernel.org
Cc: luke@diamond.org, pw@padd.com, Daniel Bingham <git@dbingham.com>
Subject: [PATCH] git-p4: Fetch the proper revision of utf16 files
Date: Fri, 3 Apr 2015 14:13:46 -0700 [thread overview]
Message-ID: <1428095627-8772-1-git-send-email-git@dbingham.com> (raw)
I discovered what appears to be a bug with the handling of utf16 type files
when cloning from P4. It appears that it always fetches the content of the
latest version rather than getting the revision specified in the changelist
being processed. This patch is an attempt to resolve that by formatting
the print command using the revision number as is done in streamP4Files().
Daniel Bingham (1):
git-p4: Fetch the proper revision of utf16 files
git-p4.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.3.5
next reply other threads:[~2015-04-03 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 21:13 Daniel Bingham [this message]
2015-04-03 21:13 ` [PATCH] git-p4: Fetch the proper revision of utf16 files Daniel Bingham
2015-04-03 21:46 ` Eric Sunshine
2015-04-03 22:49 ` Domain Admin
[not found] ` <CAFzU1R+m8Gw3O_HHKmKq0rTALh+TJ1kK84=L2rsGCNft4XcT=Q@mail.gmail.com>
2015-04-03 22:49 ` Eric Sunshine
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=1428095627-8772-1-git-send-email-git@dbingham.com \
--to=daniel@dbingham.com \
--cc=git@dbingham.com \
--cc=git@vger.kernel.org \
--cc=luke@diamond.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).