From: ALBERTIN TIMOTHEE p1514771 <firstname.lastname@example.org>
To: Junio C Hamano <email@example.com>,
MOY MATTHIEU <firstname.lastname@example.org>
Cc: BENSOUSSAN--BOHM DANIEL p1507430
Michael Haggerty <email@example.com>,
Jordan DE GEA <firstname.lastname@example.org>,
PAYRE NATHAN p1508475 <email@example.com>
Subject: RE: [PATCH v2] doc: add triangular workflow
Date: Fri, 15 Dec 2017 15:46:47 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
>>> +This workflow is commonly used on different platforms like BitBucket,
>>> +GitHub or GitLab which provide a dedicated mechanism for requesting merges.
>> As a user, I find it terribly frustrating when reading documentation
>> telling me that "there's a dedicated mechanism" for something without
>> telling me actually how to do it.
>Also I think the description is backwards from end-user's point of
>view. It's not that it is common to use the workflow on these
>hosting sites. It's more like people use the workflow and adopt use
>of these hosting sites as one building block of the workflow.
I'm wondering if this sentence is really useful. It's not essential
and it will take lot of time and space to talk about it properly.
So, if you agree, we'll erase it.
>>> +If **PUBLISH** doesn't exist, a contributor can publish his own repository.
>>> +**PUBLISH** contains modifications before integration.
>I am not sure what this really means. Isn't it the norm to create a
>place to publish your work (and only your work) for your own use?
>IOW, the above two lines solicit questions like "So... what happens
>when publish does already exist??? and where does that publish
>repository come from???"
In the case of a triangular workflow, if the project already exists,
PUBLISH will already exist too. However, if the project doesn't exist
it is at the creator charge to create it. In fact, we just explain
how doing it if the project already exist. We'll add it for the
BTW, the line : * `git push` is useless.
Thank you for the review
next prev parent reply other threads:[~2017-12-15 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 9:42 [PATCH] doc: clarify triangular workflow Timothee Albertin
2017-12-03 6:36 ` Junio C Hamano
2017-12-07 9:26 ` BENSOUSSAN--BOHM DANIEL p1507430
[not found] ` <24f652b96fd940ee91e2741830382a72@BPMBX2013-01.univ-lyon1.fr>
2017-12-07 12:43 ` Matthieu Moy
2017-12-07 15:31 ` Junio C Hamano
2017-12-14 10:48 ` [PATCH v2] doc: add " Daniel Bensoussan
[not found] ` <9a0556ac403845f39a564bbc55df5b3a@BPMBX2013-01.univ-lyon1.fr>
2017-12-14 15:04 ` Matthieu Moy
2017-12-14 20:47 ` Junio C Hamano
2017-12-15 15:46 ` ALBERTIN TIMOTHEE p1514771 [this message]
[not found] ` <eca47dd3598045a1a3fac94f9df8e972@BPMBX2013-01.univ-lyon1.fr>
2017-12-15 16:04 ` Matthieu Moy
2017-12-15 15:18 ` ALBERTIN TIMOTHEE p1514771
[not found] ` <130319f3e40c4bfb81d2fc37bb4a4f9f@BPMBX2013-01.univ-lyon1.fr>
2017-12-15 15:54 ` Matthieu Moy
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:
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 \
* 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
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).