From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Emacs Development <Emacs-devel@gnu.org>, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: Accessible "building from source" instructions
Date: Sun, 26 May 2019 12:54:00 +0200 [thread overview]
Message-ID: <87h89hpjuf.fsf@igel.home> (raw)
In-Reply-To: <eec4ed9f-4ae0-3033-7b60-2cc01b9c5505@cs.ucla.edu> (Paul Eggert's message of "Sun, 26 May 2019 03:01:37 -0700")
On Mai 26 2019, Paul Eggert <eggert@cs.ucla.edu> wrote:
> Andreas Schwab wrote:
>
>> You can pass config options also via git -c.
>
> Sure, but won't you need to pass those options each time you invoke git?
You can modify the repository config without clobbering the global
config.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-05-26 10:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 23:34 Accessible "building from source" instructions Dmitry Gutov
2019-05-26 0:25 ` T.V Raman
2019-05-26 8:19 ` Dmitry Gutov
2019-05-26 1:30 ` Paul Eggert
2019-05-26 8:20 ` Dmitry Gutov
2019-05-26 8:50 ` Paul Eggert
2019-05-26 10:18 ` Dmitry Gutov
2019-05-26 14:46 ` Eli Zaretskii
2019-05-26 20:08 ` Paul Eggert
2019-05-27 2:29 ` Eli Zaretskii
2019-05-27 16:59 ` Paul Eggert
2019-05-27 17:12 ` web pages in CVS [was Re: Accessible "building from source" instructions] Glenn Morris
2019-05-27 17:24 ` Accessible "building from source" instructions Eli Zaretskii
2019-05-27 20:17 ` Richard Stallman
2019-05-27 20:11 ` Richard Stallman
2019-05-26 9:23 ` Andreas Schwab
2019-05-26 10:01 ` Paul Eggert
2019-05-26 10:54 ` Andreas Schwab [this message]
2019-05-26 20:11 ` Paul Eggert
2019-05-26 20:19 ` Andreas Schwab
2019-05-27 4:55 ` Paul Eggert
2019-05-26 2:42 ` Eli Zaretskii
2019-05-26 8:25 ` Dmitry Gutov
2019-05-26 16:36 ` Eli Zaretskii
2019-05-26 22:10 ` Dmitry Gutov
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=87h89hpjuf.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Emacs-devel@gnu.org \
--cc=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.