git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-rev-list in local commit order

From
TGThomas Gleixner <tglx@linutronix.de>
Date
May 17, 2005, 09:52 UTC
Message-ID
<1116323520.17296.12.camel@tglx.tec.linutronix.de>
In-Reply-To
<Pine.LNX.4.58.0505161638090.18337@ppc970.osdl.org>
On Mon, 2005-05-16 at 16:46 -0700, Linus Torvalds wrote:
Show 8 quoted lines
> Yes. I'm not ahuge fan of the notion of "repo ID's". One reason is that I
> actually really really like the notion of anonymous repositories, so that
> when I do something stupid, and blow away one of my less successful
> repositories and continue with another one, nobody ever sees it (and yes,
> this happens - in my BK usage I occasionally cloned my repo for some
> testing, and then ended up using the _cloned_ repo for the real work, and
> totally blowing away ymy original one, and renamed my cloned one back to
> where my main one is).

What you blow away is a work space. But at the end you push the result of whatever work space you kept into a public available repository. Also BK stores a somewhat hidden repository (not workspace) id.

My idea of repository id was not the notion of workspace seperation. I dont care in which directory and on which machine you or who ever commits a line of code. I care where the change appears in a public repository, which is unique.

Show 6 quoted lines
> I don't see why people don't just use the "committer" name for this.  
> That's really what you want, and it ends up being a very good
> approximation of "repository ID" for a commit. Sure, people end up having
> multiple reposiories, and thus you'll occasionally see merges that end up
> merging two heads with the same "repo ID", but does anybody really care? I
> doubt it.

I came up with this after I started "git tracker" and David Woodhouse asked me to make it possible to look at the history of his repository from the repositiory POV rather than from the cloned global history of torvalds/linux-2.6.git.

Sure I have retrieved the information from committer name and committer mail, but when I tried to do the same with Dave Millers and Gregs repositories it turned out to be impossible as they use the same name/mail for each of their repositories.

Show 12 quoted lines
> For example, if you have a company Q&A policy that says that you want to 
> keep commits to different repos separate, just make sure that those repos 
> are on different machines or are accessed with different users. Or write 
> some simple wrapper scripts that make sure to set GIT_COMMITTER_EMAIL to 
> the proper value (say, the wrapper could be as simple as
> 
> 	#!/bin/sh
> 	export GIT_COMMITTER_EMAIL=$(cat .git/committer_email)
> 	real-git-commit "$@"
> 
> and then you just create a ".git/committer_email" file per repository that 
> contains the "repo ID" you want to fake.

Might be a workable solution. I would prefer if this would be a part of the core plumbing. Would you accept a patch for commit-tree which tries to check this file for existance and use the content in case its there?

tglx
Previous: Linus TorvaldsNext: Linus Torvalds
Message 13 of 17 in “git-rev-list in local commit order”
  1. SeanMay 14, 2005
  2. Thomas GleixnerMay 15, 2005
  3. SeanMay 15, 2005
  4. Thomas GleixnerMay 15, 2005
  5. SeanMay 15, 2005
  6. Thomas GleixnerMay 15, 2005
  7. SeanMay 15, 2005
  8. Thomas GleixnerMay 15, 2005
  9. SeanMay 15, 2005
  10. Thomas GleixnerMay 15, 2005
  11. SeanMay 16, 2005
  12. Linus TorvaldsMay 16, 2005
  13. Thomas GleixnerMay 17, 2005
  14. Linus TorvaldsMay 17, 2005
  15. Thomas GleixnerMay 17, 2005
  16. Linus TorvaldsMay 17, 2005
  17. Jon SeymourMay 18, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.