From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH v3 4/7] remote-bzr: update working tree
Date: Thu, 13 Dec 2012 15:58:34 -0800 [thread overview]
Message-ID: <7vhanpwllh.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vobhxwm3n.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 13 Dec 2012 15:47:40 -0800")
Junio C Hamano <gitster@pobox.com> writes:
>> Perhaps. It's not really clear if we should update the working tree at
>> all. A 'git push' doesn't update the working directory on the remote,
>> but a 'bzr push' does. I thought it was better to leave this
>> distinction clear, in case this becomes an issue later on.
> ...
> ... I don't mind rephrasing that four lines and amend the
> log message of what I have in 'pu', if that is what you want.
... which may look like this.
remote-bzr: update working tree upon pushing
A 'git push' doesn't update the working directory on the remote, but
a 'bzr push' does. Teach the remote helper for bzr to update the
working tree on the bzr side upon pushing via the "export" command.
Let me know if I grossly misinterpreted/misrepresented what you
wanted to do in this patch.
Thanks.
next prev parent reply other threads:[~2012-12-13 23:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 14:19 [PATCH v3 0/7] New remote-bzr remote helper Felipe Contreras
2012-11-11 14:19 ` [PATCH v3 1/7] Add new remote-bzr transport helper Felipe Contreras
2012-11-11 14:19 ` [PATCH v3 2/7] remote-bzr: add support for pushing Felipe Contreras
2012-11-11 14:19 ` [PATCH v3 3/7] remote-bzr: add support for remote repositories Felipe Contreras
2012-11-11 14:19 ` [PATCH v3 4/7] remote-bzr: update working tree Felipe Contreras
2012-11-28 17:38 ` Junio C Hamano
2012-12-13 22:08 ` Felipe Contreras
2012-12-13 23:47 ` Junio C Hamano
2012-12-13 23:58 ` Junio C Hamano [this message]
2012-12-14 0:52 ` Felipe Contreras
2012-11-11 14:19 ` [PATCH v3 5/7] remote-bzr: add simple tests Felipe Contreras
2012-11-28 17:36 ` Junio C Hamano
2012-11-11 14:19 ` [PATCH v3 6/7] remote-bzr: add support for fecthing special modes Felipe Contreras
2012-11-11 14:19 ` [PATCH v3 7/7] remote-bzr: add support to push " Felipe Contreras
2012-11-24 10:21 ` [PATCH v3 0/7] New remote-bzr remote helper Felipe Contreras
2012-11-26 4:09 ` Junio C Hamano
2012-11-26 11:34 ` Felipe Contreras
2012-11-27 23:32 ` Junio C Hamano
2012-11-28 0:23 ` Felipe Contreras
2012-11-28 1:56 ` Junio C Hamano
2012-11-28 2:18 ` Felipe Contreras
2012-11-28 2:37 ` Junio C Hamano
2012-11-28 3:05 ` Felipe Contreras
2012-11-28 7:01 ` Junio C Hamano
2012-11-28 7:42 ` Felipe Contreras
2012-11-28 0:42 ` Felipe Contreras
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=7vhanpwllh.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).