| commit | ac053c02029d88c7ed4d7e92949a1586eb3f7704 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 1 Aug 2007 14:23:08 +0000 (1 10:23 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 19 Aug 2007 07:38:36 +0000 (19 03:38 -0400) | ||
| tree | 84e5e58df838e7f27d8cee33cb1fae6d0f7b6917 | treesnapshot (tar.gz zip) |
| parent | 1fdb649c6ac4cfc536983077b4851a1959cbc1c4 | commitdiff |
Allow frontends to bidirectionally communicate with fast-import
The existing checkpoint command is very useful to force fast-import
to dump the branches out to disk so that standard Git tools can
access them and the objects they refer to. However there was not a
way to know when fast-import had finished executing the checkpoint
and it was safe to read those refs.
The progress command can be used to make fast-import output any
message of the frontend's choosing to standard out. The frontend
can scan for these messages using select() or poll() to monitor a
pipe connected to the standard output of fast-import.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
The existing checkpoint command is very useful to force fast-import
to dump the branches out to disk so that standard Git tools can
access them and the objects they refer to. However there was not a
way to know when fast-import had finished executing the checkpoint
and it was safe to read those refs.
The progress command can be used to make fast-import output any
message of the frontend's choosing to standard out. The frontend
can scan for these messages using select() or poll() to monitor a
pipe connected to the standard output of fast-import.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| Documentation/git-fast-import.txt | diffblobblamehistory | |
| fast-import.c | diffblobblamehistory | |
| t/t9300-fast-import.sh | diffblobblamehistory |