From: "Martin Ågren" <martin.agren@gmail.com>
To: Daniel Bensoussan <danielbensoussanbohm@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Daniel Bensoussan <daniel.bensoussan--bohm@etu.univ-lyon1.fr>,
Michael Haggerty <mhagger@alum.mit.edu>,
Jordan DE GEA <jordan.de-gea@grenoble-inp.org>,
Matthieu Moy <matthieu.moy@univ-lyon1.fr>,
Timothee Albertin <timothee.albertin@etu.univ-lyon1.fr>,
Nathan Payre <nathan.payre@etu.univ-lyon1.fr>
Subject: Re: [PATCH 2/2] Triangular workflow
Date: Fri, 17 Nov 2017 22:15:36 +0100 [thread overview]
Message-ID: <CAN0heSoJissfQqO9sDi1sHut7a-tfFcQgkcUD=QLa+5F0F9PbA@mail.gmail.com> (raw)
In-Reply-To: <20171117160759.6397-2-daniel.bensoussan--bohm@etu.univ-lyon1.fr>
On 17 November 2017 at 17:07, Daniel Bensoussan
<danielbensoussanbohm@gmail.com> wrote:
> The documentation about triangular workflow was not clear enough.
I think you would be able to `git rebase -i` these two patches into a
single, perfect patch. ;-) Maybe in collaboration with Albertin?
> -===========================
> -`git config push.default current`
> -===========================
> +============================
> +`git clone <UPSTREAM_url>`
> +`git remote add **PUBLISH**`
> +`git push`
> +============================
This renders as a single line for me, including "**PUBLISH**". (I use
AsciiDoctor, does this look good with AsciiDoc, I wonder?)
I've never worked with triangular workflows. That means I can't judge
the correctness of this, but what I've read seems reasonable and
helpful. I dropped some comments along the way, I hope you'll find them
constructive.
Martin
next prev parent reply other threads:[~2017-11-17 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 16:07 [PATCH 1/2] Documentation about triangular workflow Daniel Bensoussan
2017-11-17 16:07 ` [PATCH 2/2] Triangular workflow Daniel Bensoussan
2017-11-17 21:15 ` Martin Ågren [this message]
2017-11-17 20:01 ` [PATCH 1/2] Documentation about triangular workflow Stefan Beller
2017-11-17 21:11 ` Martin Ågren
2017-11-22 15:13 ` ALBERTIN TIMOTHEE p1514771
2017-11-18 1:33 ` Junio C Hamano
2017-11-22 15:55 ` ALBERTIN TIMOTHEE p1514771
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='CAN0heSoJissfQqO9sDi1sHut7a-tfFcQgkcUD=QLa+5F0F9PbA@mail.gmail.com' \
--to=martin.agren@gmail.com \
--cc=daniel.bensoussan--bohm@etu.univ-lyon1.fr \
--cc=danielbensoussanbohm@gmail.com \
--cc=git@vger.kernel.org \
--cc=jordan.de-gea@grenoble-inp.org \
--cc=matthieu.moy@univ-lyon1.fr \
--cc=mhagger@alum.mit.edu \
--cc=nathan.payre@etu.univ-lyon1.fr \
--cc=timothee.albertin@etu.univ-lyon1.fr \
/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).