From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 0/8] fix scp and reintroduce source-check target
Date: Mon, 4 Feb 2019 19:24:00 +0100 [thread overview]
Message-ID: <20190204192400.6f2205e3@windsurf> (raw)
In-Reply-To: <20190204180553.18394-1-patrickdepinguin@gmail.com>
On Mon, 4 Feb 2019 19:05:45 +0100
Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> After the overwhelming support for 'source-check' at the Buildroot Developer
> Days ;-) , here is a second iteration of this series.
:-)
> The first commit is actually a bugfix separate from source-check. In v1 of this
> series it was also included as the second of two 'scp'-related bugfixes, but it
> seems only the first bug-fix was applied at that time, which I hadn't realized
> until now.
>
> Patches 2-8 are the actual source-check releated ones.
> For git, svn, bzr and cvs, there is no actual implementation which means that
> the corresponding download scripts will perform the standard download logic,
> which will also verify the validity of the specified revision on the remote
> server, but not as optimal as for the other methods.
What are the changes from v1 ? I don't see a changelog here or in the
patches themselves.
Perhaps you were overwhelmingly impatient to send this v2 that you
forgot the changelog ? :-)
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-04 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 18:05 [Buildroot] [PATCHv2 0/8] fix scp and reintroduce source-check target Thomas De Schampheleire
2019-02-04 18:05 ` [Buildroot] [PATCHv2 1/8] support/download/scp: fix download with scheme prefix 'scp://' Thomas De Schampheleire
2019-02-05 19:33 ` Peter Korsgaard
2019-02-18 22:20 ` Peter Korsgaard
2019-02-04 18:05 ` [Buildroot] [PATCHv2 2/8] support/download: reintroduce 'source-check' target Thomas De Schampheleire
2019-02-09 16:47 ` Arnout Vandecappelle
2019-02-09 20:08 ` Thomas De Schampheleire
2019-02-04 18:05 ` [Buildroot] [PATCHv2 3/8] support/download/hg: implement source-check Thomas De Schampheleire
2019-02-04 18:05 ` [Buildroot] [PATCHv2 4/8] support/download/wget: " Thomas De Schampheleire
2019-02-04 18:05 ` [Buildroot] [PATCHv2 5/8] support/download/file: " Thomas De Schampheleire
2019-02-04 18:05 ` [Buildroot] [PATCHv2 6/8] Config.in: reintroduce BR2_SSH Thomas De Schampheleire
2019-02-04 18:05 ` [Buildroot] [PATCHv2 7/8] support/download/scp: implement source-check Thomas De Schampheleire
2019-02-09 16:48 ` Arnout Vandecappelle
2019-02-09 20:16 ` Thomas De Schampheleire
2019-02-04 18:05 ` [Buildroot] [PATCHv2 8/8] support/download/{bzr, cvs, git, svn}: highlight unimplemented source-check Thomas De Schampheleire
2019-02-04 18:24 ` Thomas Petazzoni [this message]
2019-02-04 18:41 ` [Buildroot] [PATCHv2 0/8] fix scp and reintroduce source-check target Thomas De Schampheleire
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=20190204192400.6f2205e3@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