Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	tglx@linutronix.de, git@vger.kernel.org,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: History messup
Date: Wed, 11 May 2005 22:31:22 +0200	[thread overview]
Message-ID: <20050511203122.GD22686@pasky.ji.cz> (raw)
In-Reply-To: <1115665598.12012.422.camel@baythorne.infradead.org>

Dear diary, on Mon, May 09, 2005 at 09:06:38PM CEST, I got a letter
where David Woodhouse <dwmw2@infradead.org> told me that...
> On Mon, 2005-05-09 at 12:01 -0700, H. Peter Anvin wrote:
> > 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.
> 
> Of course it isn't. But neither is the meaning "a committer" or 
> "an author" or even "a date".
> 
> Including some kind of repo-specific identifier with each commit would
> help us to make sense of the history, just as those other fields do.

FWIW, I recently added .git/branch-name to Cogito, since I needed some
identifier through which to differentiate between the branches
(repositories - it's all blurred in Cogito view) when sending commits
to CIA.

It is strictly per-branch (never to be shared by multiple repositories),
optional, informative and more of a temporary solution for now I had to
cook together in a minute.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

      parent reply	other threads:[~2005-05-11 20:24 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
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 [this message]

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=20050511203122.GD22686@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=dwmw2@infradead.org \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    --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