From: Adam Stankiewicz <sheerun@sher.pl>
To: git@vger.kernel.org
Subject: Motd message on git cloning
Date: Sun, 18 Nov 2012 17:04:37 +0100 [thread overview]
Message-ID: <CANCidP-d0tXfo6ZsC80LmaS1CJ475rew2D7ztrx9TkNa94a-uw@mail.gmail.com> (raw)
I'm dreaming about git feature that shows custom message on git clone.
It would be extremely helpful for informing the person cloning about
init scripts he/she need to execute (for example submodule inits or
hooks set up). For now there is no way to make sure cloning person
will receive such message (unless he/she will read the README).
The server does not need to know if it's fetch or clone, if programmer
executes git clone on client side, then the MOTD message would be
shown.
I think good candidate for MOTD message is .git/description (because
for now no one seems to care about setting repository description).
Another option is to introduce .git/motd file that would consist of
some maximum number of non-control ASCII characters.
I don't really see any security concerns. Git could filter any control
characters from MOTD out, and automation script could add --no-motd
flag. The could also be limit on MOTD file size so no one could
"flood" the terminal window with MOTD messages.
Also it's important to me that such message would be shown
automatically by default and could be turned off, not the other way
(for example --motd flag).
Some other tools like brew package manager have this feature from the
beginning and I find it extremely helpful.
What do you think?
next reply other threads:[~2012-11-18 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 16:04 Adam Stankiewicz [this message]
2012-11-18 16:34 ` Motd message on git cloning Drew Northup
2012-11-18 16:51 ` Adam Stankiewicz
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=CANCidP-d0tXfo6ZsC80LmaS1CJ475rew2D7ztrx9TkNa94a-uw@mail.gmail.com \
--to=sheerun@sher.pl \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).