From: John Keeping <john@metanate.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH] download/git: ban branch references
Date: Fri, 21 Jun 2019 17:36:53 +0100 [thread overview]
Message-ID: <20190621173653.3e3c2d89@donbot> (raw)
In-Reply-To: <20190620163946.GJ2216@scaer>
Hi Yann,
On Thu, 20 Jun 2019 18:39:46 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> On 2019-06-19 16:34 +0100, John Keeping spake thusly:
> > On Wed, 19 Jun 2019 16:18:17 +0100
> > John Keeping <john@metanate.com> wrote:
> >
> > > As described in the manual, using a branch name as a version is not
> > > supported. However, nothing enforces this so it is easy to specify a
> > > branch name either accidentally or because new developers have not read
> > > through the manual.
> > >
> > > For Git it is reasonably easy to catch most violations of this rule and
> > > fail the fetch phase. This isn't intended to be a comprehensive filter
> > > (it can be bypassed with, for example, FOO_VERSION=origin/master), but
> > > should catch accidental use of a branch version and prompt switching to
> > > an immutable reference.
> > >
> > > Signed-off-by: John Keeping <john@metanate.com>
> > > ---
> >
> > Just after sending this, I realised that the patch below doesn't work
> > for versions specified as a SHA1.
>
> I was going to reply to your original pathc, but since you noticed the
> issue on your own :-) here is some additional feedback.
>
> The sha1-as-branch is becuase of the so-called special refs. I already
> sent a patch some time ago, but did not get around to respinning it,
> which was followed by a patch to drop local branches altogether now:
> and finally a patch to detect and abort when the cset was a branch:
>
> https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/dl-git-no-branch-3
> https://git.buildroot.org/~ymorin/git/buildroot/commit/?h=yem/dl-git-no-branch-3&id=6d82e95e6d2de17370734d9253ed11a81bb750f9
> https://git.buildroot.org/~ymorin/git/buildroot/commit/?h=yem/dl-git-no-branch-3&id=5788d8dcb46ccbb595a62568ee47bbce07563dd5
> https://git.buildroot.org/~ymorin/git/buildroot/commit/?h=yem/dl-git-no-branch-3&id=f5a962bcfe481ac3edba0d04ddc06369fa54e8de
>
> So. if you're still interested in the topic, feel fre eto draw
> inspiration from the above if you think they may be helpful.
>
> There is some feedback on those somewhere on the list.
Thanks for these pointers, I found the related thread [1] and the
discussion there was really helpful.
What I propose is that we change our repository setup to essentially
mirror the remote (we can't clone with "--mirror" as that creates a bare
repo). This means we change the fetch command to:
git fetch origin --prune refs/*:refs/*
and remove the explicit fetch of $cset.
Since this fetches everything it allows the version to be the SHA-1 of a
special ref like a pull request or Gerrit changeset, which is a use case
Ricardo mentioned in the thread at [1].
We can then filter out non-tags with:
case $(git rev-parse --symbolic-full-name "${cset}") in
refs/tags/*
: ok
;;
refs/*
printf >&2 "Refusing to use Git branch '%s'.\n" "${cset}"
;;
# Anything else is not a ref, must be a raw hash which is ok.
esac
What do you think?
Regards,
John
[1] http://buildroot-busybox.2317881.n4.nabble.com/PATCH-0-3-download-detect-and-refuse-git-branch-by-name-td200050.html
next prev parent reply other threads:[~2019-06-21 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 15:18 [Buildroot] [RFC PATCH] download/git: ban branch references John Keeping
2019-06-19 15:34 ` John Keeping
2019-06-20 16:39 ` Yann E. MORIN
2019-06-21 16:36 ` John Keeping [this message]
2019-06-22 7:47 ` Yann E. MORIN
2019-06-24 11:30 ` John Keeping
2019-06-24 11:32 ` [Buildroot] [PATCH v2 1/2] download/git: fetch all refs from the remote John Keeping
2019-06-24 11:32 ` [Buildroot] [PATCH v2 2/2] download/git: ban branch references John Keeping
2019-12-29 22:12 ` Yann E. MORIN
2020-01-02 17:57 ` John Keeping
2019-12-29 22:03 ` [Buildroot] [PATCH v2 1/2] download/git: fetch all refs from the remote Yann E. MORIN
2019-06-20 17:27 ` [Buildroot] [RFC PATCH] download/git: ban branch references Joel Carlson
2019-06-21 12:36 ` John Keeping
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=20190621173653.3e3c2d89@donbot \
--to=john@metanate.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