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

Creating own hierarchies under $GITDIR/refs ?

From
David Kastrup <dak@gnu.org>
Date
Feb 2, 2014, 10:37 UTC
Message-ID
<87a9e92424.fsf@fencepost.gnu.org>
Hi,

in the context of an ongoing discussion on the Emacs developer list of converting the Bzr repository of Emacs, one question (with different approaches) is where to put the information regarding preexisting Bazaar revision numbers and bug tracker ids: those are not present in the current Git mirror.

Putting them in the commit messages would require a full history rewrite, and if some are missed in the process, this cannot be fixed afterwards.

So I mused: refs/heads contains branches, refs/tags contains tags. The respective information would likely easily enough be stored in refs/bzr and refs/bugs and in that manner would not pollute the "ordinary" tag and branch spaces, rendering "git tag" and/or "git branch" output mostly unusable. I tested creating such a directory and entries and indeed references like bzr/39005 then worked.

However, cloning from the repository did not copy those directories and references, so without modification, this scheme would not work for cloned repositories.

Are there some measures one can take/configure in the parent repository such that (named or all) additional directories inside of $GITDIR/refs would get cloned along with the rest?

It would definitely open viable options for dealing with mirrors and/or repository migrations in general.

-- 
David Kastrup
Next: Duy Nguyen
Message 1 of 11 in “Creating own hierarchies under $GITDIR/refs ?”
  1. David KastrupFeb 2, 2014
  2. Duy NguyenFeb 2, 2014
  3. David KastrupFeb 2, 2014
  4. John KeepingFeb 2, 2014
  5. David KastrupFeb 2, 2014
  6. John KeepingFeb 2, 2014
  7. Jed BrownFeb 2, 2014
  8. Duy NguyenFeb 2, 2014
  9. David KastrupFeb 2, 2014
  10. Andreas SchwabFeb 2, 2014
  11. Jeff KingFeb 2, 2014

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.