From: Vitor Antunes <vitor.hda@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Pete Wyckoff <pw@padd.com>,
git@vger.kernel.org, Luke Diamand <luke@diamand.org>
Subject: Re: [PATCH 1/2] git-p4: Test changelists touching two branches
Date: Fri, 25 May 2012 09:32:29 +0100 [thread overview]
Message-ID: <CAOpHH-U5dRaMsMPn3X6KujSb=pnw+voaOLaEntGhi+4x1uboGA@mail.gmail.com> (raw)
In-Reply-To: <7vmx4xunzr.fsf@alter.siamese.dyndns.org>
On Fri, May 25, 2012 at 1:02 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Vitor Antunes <vitor.hda@gmail.com> writes:
>
>> What about the parentheses in the next line, is it necessary? Or can I
>> simply remove that pair of parentheses and unindent the code in
>> between?
>>
>>> ...
>>>> + (
>>>> + cd "$cli" &&
>>>> + p4 integrate //depot/branch3/file3 //depot/branch4/file3 &&
>>>> + p4 delete //depot/branch3/file3 &&
>>>> + p4 submit -d "Move branch3/file3 to branch4/file3"
>>>> + )
>>>> +'
>
> If you mean this part, the parentheses to throw you into a subprocess are
> required. Otherwise, a failure in any of these three p4 commands will
> leave you in $cli directory, causing the next test to start in a directory
> that it does not expect.
That makes sense and is quite obvious now that I _see_ it.
Thanks for your help Junio.
Vitor
next prev parent reply other threads:[~2012-05-25 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 23:38 [PATCH 0/2] git-p4: New test cases for branch detection Vitor Antunes
2012-05-22 23:38 ` [PATCH 1/2] git-p4: Test changelists touching two branches Vitor Antunes
2012-05-24 1:08 ` Pete Wyckoff
2012-05-24 22:42 ` Vitor Antunes
2012-05-25 0:02 ` Junio C Hamano
2012-05-25 8:32 ` Vitor Antunes [this message]
2012-05-22 23:38 ` [PATCH 2/2] git-p4: Verify detection of "empty" branch creation Vitor Antunes
2012-05-24 1:13 ` 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='CAOpHH-U5dRaMsMPn3X6KujSb=pnw+voaOLaEntGhi+4x1uboGA@mail.gmail.com' \
--to=vitor.hda@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).