From: Johannes Sixt <j.sixt@viscovery.net>
To: "Jørgen Edelbo" <jed@napatech.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"spearce@spearce.org" <spearce@spearce.org>,
"hvoigt@hvoigt.net" <hvoigt@hvoigt.net>,
Pat Thoyts <patthoyts@gmail.com>
Subject: Re: [PATCH] git-gui: Modify push dialog to support Gerrit review
Date: Thu, 05 Sep 2013 10:57:14 +0200 [thread overview]
Message-ID: <5228476A.2070505@viscovery.net> (raw)
In-Reply-To: <F8C23E99F5C6884EB99E2A1966D743637F3619A6@cph-gen-exch01.napatech.com>
Please do not top-post.
Am 9/5/2013 10:29, schrieb Jørgen Edelbo:
> -----Original Message----- From: Johannes Sixt
>> Am 9/2/2013 10:54, schrieb Joergen Edelbo:
>>> Changes done:
>>>
>>> Remove selection of branches to push - push always HEAD. This can be
>>> justified by the fact that this far the most common thing to do.
>>
>> What are your plans to support a topic-based workflow? "Far the most
>> common thing to happen" is that someone forgets to push completed
>> topics. With this change, aren't those people forced to relinguish
>> their current work because they have to checkout the completed topics
>> to push them?
>
> I am not quite sure what your concern is.
When I have completed topics A and B, but forgot to push them, and now I
am working on topic C, how do I push topics A and B?
You say I can only push HEAD. I understand this that I have to stop work
on C (perhaps commit or stash any unfinished work), then checkout A, push
it, checkout B, push it, checkout C and unstash the unfinished work. If my
understanding is correct, the new restriction is a no-go.
-- Hannes
next prev parent reply other threads:[~2013-09-05 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 8:54 [PATCH] git-gui: Modify push dialog to support Gerrit review Joergen Edelbo
2013-09-05 6:20 ` Heiko Voigt
2013-09-05 6:42 ` Johannes Sixt
2013-09-05 8:29 ` Jørgen Edelbo
2013-09-05 8:57 ` Johannes Sixt [this message]
2013-09-05 9:18 ` Jørgen Edelbo
2013-09-05 9:31 ` Johannes Sixt
2013-09-05 17:34 ` Junio C Hamano
2013-09-06 8:17 ` Jørgen Edelbo
2013-09-05 21:04 ` Heiko Voigt
2013-09-05 18:19 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2013-09-06 10:30 Joergen Edelbo
2013-09-06 21:49 ` Phil Hord
2013-09-07 17:03 ` Jørgen Edelbo
2013-09-12 9:21 Joergen Edelbo
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=5228476A.2070505@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=jed@napatech.com \
--cc=patthoyts@gmail.com \
--cc=spearce@spearce.org \
/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).