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

Re: Creating own hierarchies under $GITDIR/refs ?

From
Duy Nguyen <pclouds@gmail.com>
Date
Feb 2, 2014, 11:00 UTC
Message-ID
<CACsJy8CdKRQ_au3QqVoUdedvPpkPh_2vodKJwLZ7VrrwRJSDXQ@mail.gmail.com>
In-Reply-To
<87a9e92424.fsf@fencepost.gnu.org>
On Sun, Feb 2, 2014 at 5:37 PM, David Kastrup <dak@gnu.org> wrote:
Show 9 quoted lines
> 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.

What do you need them for? Perhaps putting everything in a file, maybe sorted by SHA-1, would suffice? It should not be too hard to write a script to map bug tracker id to a commit id. The file is for past commits only. New commits can contain these info in their messages.

-- 
Duy
Previous: David KastrupNext: David Kastrup
Message 2 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.