From: Pavel Roskin <proski@gnu.org>
To: sean <seanlkml@sympatico.ca>
Cc: Junio C Hamano <junkio@cox.net>,
torvalds@osdl.org, Johannes.Schindelin@gmx.de,
git@vger.kernel.org
Subject: Re: Implementing branch attributes in git config
Date: Tue, 09 May 2006 19:23:51 -0400 [thread overview]
Message-ID: <1147217031.21611.4.camel@dv> (raw)
In-Reply-To: <20060509184519.5a707231.seanlkml@sympatico.ca>
On Tue, 2006-05-09 at 18:45 -0400, sean wrote:
> On Tue, 09 May 2006 15:42:25 -0700
> Junio C Hamano <junkio@cox.net> wrote:
> > Does this mean you can have anything other than LF and ']'?
>
> Anything but LF; how's this for ugly:
>
> ["hello Worl\]d \\backslash]
Actually, LF is already handled just fine in the value part:
[proski@dv .git]$ git-repo-config s1.k1 $'v1\nv2'
[proski@dv .git]$ grep [sk]1 config
[s1]
k1 = v1\nv2
Note that quoting doesn't solve this problem (unless multi-line section
headers are allowed), but backslash escaping does.
But I guess everybody prefers quotes for their friendly look.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-05-09 23:24 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 21:34 Implementing branch attributes in git config Pavel Roskin
2006-05-07 22:24 ` Junio C Hamano
2006-05-08 0:43 ` Johannes Schindelin
2006-05-08 0:05 ` Linus Torvalds
2006-05-08 0:18 ` Linus Torvalds
2006-05-08 0:25 ` Linus Torvalds
2006-05-08 1:05 ` Johannes Schindelin
2006-05-08 1:21 ` Pavel Roskin
2006-05-08 1:27 ` Johannes Schindelin
2006-05-08 1:55 ` Pavel Roskin
2006-05-08 9:00 ` Junio C Hamano
2006-05-08 12:17 ` Johannes Schindelin
2006-05-08 15:15 ` Pavel Roskin
2006-05-08 0:34 ` sean
2006-05-08 0:34 ` sean
2006-05-08 0:55 ` Linus Torvalds
2006-05-08 1:04 ` Pavel Roskin
2006-05-08 1:11 ` sean
2006-05-08 1:11 ` sean
2006-05-08 0:36 ` Pavel Roskin
2006-05-08 0:43 ` Linus Torvalds
2006-05-08 1:27 ` Junio C Hamano
2006-05-08 1:34 ` sean
2006-05-08 1:34 ` sean
2006-05-08 1:45 ` Johannes Schindelin
2006-05-08 1:44 ` sean
2006-05-08 1:44 ` sean
2006-05-08 2:29 ` Junio C Hamano
2006-05-08 2:39 ` sean
2006-05-08 2:39 ` sean
2006-05-08 23:20 ` Daniel Barkalow
2006-05-08 23:30 ` sean
2006-05-08 23:30 ` sean
2006-05-08 23:44 ` Johannes Schindelin
2006-05-09 0:08 ` sean
2006-05-09 0:08 ` sean
2006-05-09 0:23 ` Johannes Schindelin
2006-05-09 0:37 ` Linus Torvalds
2006-05-09 0:49 ` sean
2006-05-09 0:49 ` sean
2006-05-09 0:54 ` Junio C Hamano
2006-05-09 1:05 ` Linus Torvalds
2006-05-09 1:18 ` Junio C Hamano
2006-05-09 1:30 ` Linus Torvalds
2006-05-09 5:31 ` Junio C Hamano
2006-05-09 1:57 ` Linus Torvalds
2006-05-09 2:47 ` sean
2006-05-09 2:47 ` sean
2006-05-09 3:08 ` Linus Torvalds
2006-05-09 3:07 ` sean
2006-05-09 3:07 ` sean
2006-05-09 4:11 ` Linus Torvalds
2006-05-09 4:28 ` Jakub Narebski
2006-05-09 11:21 ` Johannes Schindelin
2006-05-09 15:29 ` Linus Torvalds
2006-05-09 18:03 ` Junio C Hamano
2006-05-09 19:24 ` Linus Torvalds
2006-05-09 19:44 ` sean
2006-05-09 19:44 ` sean
2006-05-09 22:09 ` sean
2006-05-09 22:09 ` sean
2006-05-09 22:42 ` Junio C Hamano
2006-05-09 22:45 ` sean
2006-05-09 22:45 ` sean
2006-05-09 23:07 ` sean
2006-05-09 23:07 ` sean
2006-05-09 23:23 ` Pavel Roskin [this message]
2006-05-10 0:17 ` Linus Torvalds
2006-05-10 1:08 ` sean
2006-05-10 1:08 ` sean
2006-05-10 2:08 ` Linus Torvalds
2006-05-10 7:19 ` Martin Langhoff
2006-05-10 11:07 ` Johannes Schindelin
2006-05-10 15:37 ` Linus Torvalds
2006-05-10 16:03 ` Jakub Narebski
2006-05-10 23:17 ` Martin Langhoff
2006-05-10 23:55 ` Linus Torvalds
2006-05-11 0:11 ` Linus Torvalds
2006-05-11 9:51 ` Jeff King
2006-05-11 11:39 ` Jeff King
2006-05-11 0:13 ` Martin Langhoff
2006-05-11 10:30 ` Johannes Schindelin
2006-05-11 1:53 ` Nicolas Pitre
2006-05-11 6:02 ` Jakub Narebski
2006-05-10 1:38 ` sean
2006-05-10 1:38 ` sean
2006-05-11 17:22 ` Junio C Hamano
2006-05-09 4:20 ` Pavel Roskin
2006-05-09 11:26 ` Martin Waitz
2006-05-09 11:34 ` Johannes Schindelin
2006-05-08 23:40 ` Johannes Schindelin
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=1147217031.21611.4.camel@dv \
--to=proski@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=seanlkml@sympatico.ca \
--cc=torvalds@osdl.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 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.