From: W. Trevor King wk...@tremily.us
There is no need to use here documents to setup this configuration.
It is easier, less confusing, and more robust to use Git's
configuration tools directly.
Signed-off-by: W. Trevor King wk...@tremily.us
---
Documentation/user-manual.txt | 17
W. Trevor King wk...@tremily.us writes:
From: W. Trevor King wk...@tremily.us
There is no need to use here documents to setup this configuration.
It is easier, less confusing, and more robust to use Git's
configuration tools directly.
Signed-off-by: W. Trevor King wk...@tremily.us
---
On Sun, Feb 10, 2013 at 01:33:31PM -0800, Junio C Hamano wrote:
Look at how Fetching branches from other repositories is done. It
shows the use of remote add and then shows the result by running
cat to show the contents.
I think that organization is much nicer than completely hiding how
W. Trevor King wrote:
On Sun, Feb 10, 2013 at 01:33:31PM -0800, Junio C Hamano wrote:
The resulting text may read like so:
…
I'm fine with this too, but if this is the suggested route, why bother
with `git config` at all? Is it just for ease of scripting?
Yes. It can also be helpful when
On Sun, Feb 10, 2013 at 02:08:48PM -0800, Jonathan Nieder wrote:
For everyday interactive configuration editing, config files have some
good advantages:
- The settings are easy to read, well organized, and all in one place
- The file can include comments.
I'm convinced, although the
W. Trevor King wk...@tremily.us writes:
On Sun, Feb 10, 2013 at 01:33:31PM -0800, Junio C Hamano wrote:
Look at how Fetching branches from other repositories is done. It
shows the use of remote add and then shows the result by running
cat to show the contents.
I think that organization is
6 matches
Mail list logo
