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

Re: Creating own hierarchies under $GITDIR/refs ?

From
Jed Brown <jed@59a2.org>
Date
Feb 2, 2014, 23:44 UTC
Message-ID
<878utt84g7.fsf@jedbrown.org>
In-Reply-To
<20140202122432.GC29976@serenity.lan>
John Keeping <john@keeping.me.uk> writes:
Show 8 quoted lines
> I actually wonder if you could do this with notes and git-grep; for
> example:
>
>     git grep -l keeping.me.uk refs/notes/amlog |
>     sed -e 's/.*://' -e 's!/!!g'
>
> That should be relatively efficient since you're only looking at the
> current notes tree.

I added notes handling to gitifyhg and would search it similar to this. Since gitifyhg is two-way, I could not modify the commits. Later, when we converted several repositories (up to 50k commits/80 MB), I appended

  Hg-commit: $Hg_commit_hash

to all the commit messages. This way it shows up on the web interface, users don't have to obtain the notes specially, and "git log --grep" works naturally. I think it's worth considering this simple solution; existing Git users won't mind recloning once.

Previous: John KeepingNext: Duy Nguyen
Message 7 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.