From: Dave Jones <davej@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: A shortcoming of the git repo format
Date: Wed, 27 Apr 2005 14:32:40 -0400 [thread overview]
Message-ID: <20050427183239.GE19011@redhat.com> (raw)
In-Reply-To: <426FD3EE.5000404@zytor.com>
On Wed, Apr 27, 2005 at 11:03:26AM -0700, H. Peter Anvin wrote:
> Linus Torvalds wrote:
> >
> >On Tue, 26 Apr 2005, H. Peter Anvin wrote:
> >
> >>One solution to all of this would be to define a quoting standard for
> >>strings, and simply require that all free-format strings (like the
> >>author fields) or at least strings that match [0-9a-f]{20}, are always
> >>quoted.
> >
> >
> >git uses more of the ".newsrc" format, in that it just knows which
> >characters are legal or not.
> >
> >To find the email address, look for the first '<'. To find the date, look
> >for the first '>'. Those characters are not allowed in the name or the
> >email, so they act as well-defined delimeters.
> >
>
> That's true for email addresses, but the point was to distinguish links
> to other git objects from any other kind of text. Currently there is no
> such delimiter for that.
That actually broke one of my first git scripts when one of the
changelog texts started a line with 'tree '. I hacked around it
by making my script only grep in the 'head -n4' lines, but this
seems somewhat fragile having to make assumptions that the field
I want to see is in the first 4 lines.
Dave
next prev parent reply other threads:[~2005-04-27 18:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 5:43 A shortcoming of the git repo format H. Peter Anvin
2005-04-27 15:00 ` C. Scott Ananian
2005-04-27 15:22 ` Linus Torvalds
2005-04-27 18:03 ` H. Peter Anvin
2005-04-27 18:32 ` Dave Jones [this message]
2005-04-27 18:47 ` H. Peter Anvin
2005-04-27 22:51 ` Jon Seymour
2005-04-27 19:15 ` Linus Torvalds
2005-04-27 19:39 ` Petr Baudis
2005-04-27 19:11 ` Linus Torvalds
2005-04-27 19:47 ` The " Brian O'Mahoney
2005-04-27 20:40 ` A shortcoming of the " H. Peter Anvin
2005-04-27 20:49 ` Tom Lord
2005-04-27 20:59 ` H. Peter Anvin
2005-04-28 0:57 ` Linus Torvalds
2005-04-28 1:34 ` Paul Jackson
2005-04-28 2:14 ` Tom Lord
2005-04-28 3:37 ` Ryan Anderson
2005-04-28 8:31 ` Morgan Schweers
2005-04-28 15:08 ` Barry Silverman
2005-04-27 20:56 ` Linus Torvalds
2005-04-28 0:45 ` David A. Wheeler
2005-04-28 0:46 ` David Lang
2005-04-27 23:50 ` Daniel Barkalow
2005-04-27 23:56 ` H. Peter Anvin
2005-04-28 1:51 ` Daniel Barkalow
2005-04-28 1:56 ` H. Peter Anvin
2005-04-28 13:39 ` David Woodhouse
2005-04-27 20:58 ` Gerhard Schrenk
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=20050427183239.GE19011@redhat.com \
--to=davej@redhat.com \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--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 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).