From: Stavros Ntentos <stdedos@gmail.com>
To: bagasdotme@gmail.com
Cc: git@vger.kernel.org, gitster@pobox.com, stdedos+git@gmail.com
Subject: Re: [PATCH v1 1/1] ci: facilitate dev to mimic a CI environment
Date: Sat, 27 Mar 2021 11:08:13 +0200 [thread overview]
Message-ID: <20210327090813.7847-1-133706+stdedos@users.noreply.github.com> (raw)
In-Reply-To: <5196a86c-1153-8998-a8cb-c8bd20687150@gmail.com>
> > diff --git a/Documentation/howto/setup-local-dev-environment-docker.sh b/Documentation/howto/setup-local-dev-environment-docker.sh
> > new file mode 100644
> > index 0000000000..265602ea55
> > --- /dev/null
> > +++ b/Documentation/howto/setup-local-dev-environment-docker.sh
> > @@ -0,0 +1,43 @@
> > +#!/bin/false
> Wait, why did you make this documentation /bin/false script? I think
> it is better to be in Asciidoc format (.txt)
My full intention was to actually _create_ a script that would put a
wanna-be developer (me) from (a) looking at my terminal inside git/,
to (b) have a ci-like environment, inside an abstraction layer (docker)
with linked sources (i.e. the "${PWD}:/usr/src/git" part).
However, the way sources and docker invocation are defined, I find it hard
to create "the script". Also because (again) my docker knowledge is limited.
I want future nitpick-fixers (hopefully with more docker experience),
to look at this script with such agenda in mind - and not to "just"
document their findings alongside mine.
`#!/bin/false` is simply my way of saying "it's not ready to be run yet",
and I used `.sh` to get formatting / syntax highlighting cheaper than
running a fully-fledged .md file.
If you still insist it's no good as a ".sh",
my intention would be to make it .md (to get some formatting in it).
prev parent reply other threads:[~2021-03-27 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 17:05 [PATCH v1 0/1] ci: facilitate dev to mimic a CI environment Σταύρος Ντέντος
2021-03-26 17:05 ` [PATCH v1 1/1] " Σταύρος Ντέντος
2021-03-27 6:52 ` Bagas Sanjaya
2021-03-27 9:08 ` Stavros Ntentos [this message]
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=20210327090813.7847-1-133706+stdedos@users.noreply.github.com \
--to=stdedos@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stdedos+git@gmail.com \
/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).