From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] docs/manual: expand on why using a branch name is not supported
Date: Thu, 9 Aug 2018 23:48:44 +0200 [thread overview]
Message-ID: <20180809234844.3a2a542f@windsurf> (raw)
In-Reply-To: <7f01fc03df91561ce5163e1e300d36f2c642f913.1533400367.git.yann.morin.1998@free.fr>
Hello Yann,
On Sat, 4 Aug 2018 18:33:04 +0200, Yann E. MORIN wrote:
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Following my comments, I've marked this patch as Changes Requested.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-09 21:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 16:33 [Buildroot] [PATCH 0/3] download: detect and refuse git branch by name Yann E. MORIN
2018-08-04 16:33 ` [Buildroot] [PATCH 1/3] support/download: remove help from wrapper Yann E. MORIN
2018-08-09 21:48 ` Thomas Petazzoni
2018-08-04 16:33 ` [Buildroot] [PATCH 2/3] docs/manual: expand on why using a branch name is not supported Yann E. MORIN
2018-08-04 16:36 ` Thomas Petazzoni
2018-08-09 21:48 ` Thomas Petazzoni [this message]
2018-08-04 16:33 ` [Buildroot] [PATCH 3/3] support/download: detect and abort when using a git branch by name Yann E. MORIN
2018-08-06 3:14 ` Ricardo Martincoski
2018-08-06 18:36 ` Yann E. MORIN
2018-08-07 0:39 ` Ricardo Martincoski
2018-08-12 20:25 ` Yann E. MORIN
2018-08-12 20:41 ` Thomas Petazzoni
2018-08-12 20:48 ` Yann E. MORIN
2018-08-13 14:13 ` ricardo.martincoski at gmail.com
2018-08-13 16:06 ` Yann E. MORIN
2018-08-16 1:04 ` Ricardo Martincoski
2018-08-21 20:22 ` Arnout Vandecappelle
2018-08-21 23:45 ` Ricardo Martincoski
2018-08-13 14:33 ` Ricardo Martincoski
2018-08-13 16:19 ` Yann E. MORIN
2018-08-16 3:13 ` Ricardo Martincoski
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=20180809234844.3a2a542f@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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