From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: A shortcoming of the git repo format
Date: Wed, 27 Apr 2005 13:40:36 -0700 [thread overview]
Message-ID: <426FF8C4.8080809@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504271154470.18901@ppc970.osdl.org>
Linus Torvalds wrote:
>
> No, that's definitely _not_ the point.
>
> I repeat: git does not do any free-form parsin AT ALL. The links are in
> well-defined places, and you do not ever search for them. And that's
> really very very important.
>
I know that. However, is that going to be true for all versions of the
repository format over all time? If so, the repository format is brittle.
> > Currently there is no such delimiter for that.
>
> There absolutely is.
>
> For a "commit", the format is...
My point was that with a syntactic delimiter, one can write a tool that
doesn't necessarily know everything about every tag, including future
tags which may not have been invented when the tool was written.
One can simply say "we don't do that"; finding an unknown tag is always
a fatal error. That means the format is more brittle, but brittle does
mean it breaks as opposed to getting deformed in some, potentially
undesirable way.
-hpa
next prev parent reply other threads:[~2005-04-27 20:35 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
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 ` H. Peter Anvin [this message]
2005-04-27 20:49 ` A shortcoming of the " 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=426FF8C4.8080809@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--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.