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

Help requested - trying to build a tool doing whole-tree commits

From
UUnknown <unknown@unknown.invalid>
Date
Nov 9, 2012, 18:20 UTC
Message-ID
<20121109182024.81074BC66D4@golux>
(Apologies if this arrives twice. I'm on the road, with somewhat flaky email.)

Because of my work on reposurgeon, I am sometimes asked to produce git repositories for very old projects that not only are still using CVS but have ancient releases not in the CVS repository, preserved only as tarballs. I have such a request currently pending from the robotfindskitten project.

To automate this process, I am trying to write a tool that will take a sequence of file trees and synthetic change comments in one end and emit a git repository composing them into a DAG out the other. The working name for this tool is 'gitpacker'.

I've already written the unpacking operation (git repo to tree sequence plus log). This morning I discovered that git-commit won't do quite what I need for the packing operation. I'm requesting help.

I need a command or command sequence that will commit an entire file tree to a repository...

(a) Allowing me to specify committer and author metadata, and

(b) deleting paths not present in the previous commit on the current branch, and

(c) allowing me to specify merge links from other previous commits.
git commit -a passes (a) and (b) but not (c).
Advice on how to accomplish this is requested

Advice on a better name for the tool is also requested, as I'm not happy with the way my use of 'pack' collides with existing git use of the same verb.

-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

.. a government and its agents are under no general duty to 
provide public services, such as police protection, to any 
particular individual citizen...
        -- Warren v. District of Columbia, 444 A.2d 1 (D.C. App.181)
Next: Andreas Schwab
Message 1 of 5 in “Help requested - trying to build a tool doing whole-tree commits”
  1. UnknownNov 9, 2012
  2. Andreas SchwabNov 9, 2012
  3. Felipe ContrerasNov 10, 2012
  4. Junio C HamanoNov 10, 2012
  5. Eric S. RaymondNov 11, 2012

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.