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

feature-request: git notes copy --to <ref>

From
Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Date
Feb 20, 2014, 21:03 UTC
Message-ID
<20140220210334.GM6988@pengutronix.de>
Hello,

I'm playing around with git-notes and want to share some of my notes with my co-workers. We have a central repository for our various topic branches and want to track upstream inclusion in git-notes. So we have to share our notes branch somehow.

The workflow I think makes sense here is (untested):
	### hack hack, add notes bla blub
	### -> nice topic branch with some notes
	git fetch serverrepo refs/notes/commits:refs/notes/servercommits
	git notes merge refs/notes/servercommits
	git rev-list origin/master.. | awk '{print $1 " " $1}' | git notes copy --to refs/notes/servercommits --stdin
	git push serverrepo refs/notes/servercommits:refs/notes/commits
Then maybe:
	git notes merge refs/notes/servercommits
again.

The idea here is to only include notes in refs/notes/servercommits that are relevant for my coworkers and not all intermediate notes that were created during development or while working on other branches.

Does this make sense? Do you have better ideas or suggestions how to improve the workflow?

The only problem now is that git notes copy doesn't take a --to parameter. Maybe there is a volunteer to implement it? Then I'd volunteer to test it :-)

Best regards Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Next: Uwe Kleine-König
Message 1 of 2 in “feature-request: git notes copy --to <ref>”
  1. Uwe Kleine-KönigFeb 20, 2014
  2. Uwe Kleine-KönigMar 17, 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.