From: "H. Peter Anvin" <hpa@zytor.com>
To: tglx@linutronix.de
Cc: David Woodhouse <dwmw2@infradead.org>,
git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: History messup
Date: Mon, 09 May 2005 12:01:59 -0700 [thread overview]
Message-ID: <427FB3A7.8050906@zytor.com> (raw)
In-Reply-To: <1115660903.19236.39.camel@tglx>
Thomas Gleixner wrote:
>
> That would be really great. A line after "parents" like
>
> repoid "username/reponame"
>
> would be sufficient
>
Seems like a UUID or a SHA-1 identifier would be better.
However, one can definitely argue that even the meaning of "a
repository" isn't well-defined in the context of git.
-hpa
next prev parent reply other threads:[~2005-05-09 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 16:59 History messup Thomas Gleixner
2005-05-09 17:06 ` Thomas Glanzmann
2005-05-09 18:05 ` Thomas Gleixner
2005-05-09 17:27 ` David Woodhouse
2005-05-09 17:48 ` Thomas Gleixner
2005-05-09 19:01 ` H. Peter Anvin [this message]
2005-05-09 19:06 ` David Woodhouse
2005-05-09 19:34 ` H. Peter Anvin
2005-05-09 22:08 ` Sean
2005-05-11 17:09 ` Thomas Gleixner
2005-05-11 20:31 ` Petr Baudis
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=427FB3A7.8050906@zytor.com \
--to=hpa@zytor.com \
--cc=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=tglx@linutronix.de \
--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