git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Luke Diamand <luke@diamand.org>
Cc: git@vger.kernel.org, "Andrew Oakley" <aoakley@roku.com>,
	"Romain Merland" <merlorom@yahoo.fr>,
	"SZEDER Gábor" <szeder.dev@gmail.com>,
	"Vitor Antunes" <vitor.hda@gmail.com>,
	"Andrey Mazo" <amazo@checkvideo.com>
Subject: Re: [PATCHv3 0/2] git-p4: shelved change update with move/copy
Date: Fri, 18 Jan 2019 09:46:21 -0800	[thread overview]
Message-ID: <xmqqva2lluz6.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190118093656.16521-1-luke@diamand.org> (Luke Diamand's message of "Fri, 18 Jan 2019 09:36:54 +0000")

Luke Diamand <luke@diamand.org> writes:

> This updates the patchset to support copy, as suggested by Andrey.
>
> Luke Diamand (2):
>   git-p4: add failing test for shelved CL update involving move/copy
>   git-p4: handle update of moved/copied files when updating a shelve
>
>  git-p4.py                |  2 ++
>  t/t9807-git-p4-submit.sh | 57 +++++++++++++++++++++++++++++++++++++---
>  2 files changed, 56 insertions(+), 3 deletions(-)

Thanks.

This has been listed among those that have been planned to be merged
down to 'next', which I wanted to do today.  I'll replace it with
this round and merge it in a few days.

  parent reply	other threads:[~2019-01-18 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  9:36 [PATCHv3 0/2] git-p4: shelved change update with move/copy Luke Diamand
2019-01-18  9:36 ` [PATCHv3 1/2] git-p4: add failing test for shelved CL update involving move/copy Luke Diamand
2019-01-18  9:36   ` [PATCHv3 2/2] git-p4: handle update of moved/copied files when updating a shelve Luke Diamand
2019-01-18 17:46 ` Junio C Hamano [this message]
2019-01-22 18:16 ` [PATCHv3 0/2] git-p4: shelved change update with move/copy 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqva2lluz6.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=amazo@checkvideo.com \
    --cc=aoakley@roku.com \
    --cc=git@vger.kernel.org \
    --cc=luke@diamand.org \
    --cc=merlorom@yahoo.fr \
    --cc=szeder.dev@gmail.com \
    --cc=vitor.hda@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).