version-controlled at all). But there are several disadvantages -
for one, these tools (especially StGIT) do not actually fit well
with plain Git at all: it is basically impossible to take advantage
version-controlled at all). But there are several disadvantages -
for one, these tools (especially StGIT) do not actually fit well
with plain Git at all: it is basically impossible to take advantage
these tools horribly fail in the face of distributed environment.
TopGit has been designed around three main tenets:
these tools horribly fail in the face of distributed environment.
TopGit has been designed around three main tenets:
As mentioned above, the main intended use-case for TopGit is tracking
third-party patches, where each patch is effectively a single topic
As mentioned above, the main intended use-case for TopGit is tracking
third-party patches, where each patch is effectively a single topic
you track many patches where many are independent but some depend
on others, TopGit ignores the ancient Quilt heritage of patch series
and instead allows the patches to freely form graphs (DAGs just like
you track many patches where many are independent but some depend
on others, TopGit ignores the ancient Quilt heritage of patch series
and instead allows the patches to freely form graphs (DAGs just like
to manually specify which patches does the current one depend
on, but TopGit might help you with that in the future in a darcs-like
fashion.
to manually specify which patches does the current one depend
on, but TopGit might help you with that in the future in a darcs-like
fashion.
After `tg create`, you should insert the patch description
to the '.topmsg' file, which will already contain some
After `tg create`, you should insert the patch description
to the '.topmsg' file, which will already contain some
configuration variables in order to have `tg create`
add these headers with given default values to '.topmsg'.
configuration variables in order to have `tg create`
add these headers with given default values to '.topmsg'.
its documentation for details on how to setup email for git.
You can pass arbitrary options to this command through the
'-s' parameter, but you must double-quote everything.
its documentation for details on how to setup email for git.
You can pass arbitrary options to this command through the
'-s' parameter, but you must double-quote everything.
This can take long time to accurately determine all the relevant
information about each branch; you can pass '-t' to get just
This can take long time to accurately determine all the relevant
information about each branch; you can pass '-t' to get just
- terse list of topic branch names quickly.
+ terse list of topic branch names quickly. Alternately, you can
+ pass '--graphviz' to get a dot-suitable output to draw a dependency
+ graph between the topic branches.
in the cleaned up history (corresponding basically exactly
to `tg patch` output for the topic branch).
in the cleaned up history (corresponding basically exactly
to `tg patch` output for the topic branch).
with the collapsed history, or a quilt series in new directory.
In case of producing collapsed history in new branch,
with the collapsed history, or a quilt series in new directory.
In case of producing collapsed history in new branch,
a comma-separated explicit list of branches to export. This
mode of operation is currently not supported with collapse.
a comma-separated explicit list of branches to export. This
mode of operation is currently not supported with collapse.
+ In '--quilt' mode the patches are named like the originating topgit
+ branch. So usually they end up in subdirectories of the output
+ directory. With option '--flatten' the names are mangled such that
+ they end up directly in the output dir (i.e. slashed are substituted by
+ underscores).
+
Usage: tg export ([--collapse] BRANCH | --quilt DIR)
TODO: Make stripping of non-essential headers configurable
TODO: Make stripping of [PATCH] and other prefixes configurable
TODO: --mbox option for other mode of operation
Usage: tg export ([--collapse] BRANCH | --quilt DIR)
TODO: Make stripping of non-essential headers configurable
TODO: Make stripping of [PATCH] and other prefixes configurable
TODO: --mbox option for other mode of operation
TODO: -a option to export all branches
TODO: For quilt exporting, use a temporary branch and remove it when
done - this would allow producing conflict-less series
TODO: -a option to export all branches
TODO: For quilt exporting, use a temporary branch and remove it when
done - this would allow producing conflict-less series
~~~~~~~~~
Import commits within the given revision range into TopGit,
creating one topic branch per commit, the dependencies forming
~~~~~~~~~
Import commits within the given revision range into TopGit,
creating one topic branch per commit, the dependencies forming
The branch names are auto-guessed from the commit messages
and prefixed by t/ by default; use '-p PREFIX' to specify
The branch names are auto-guessed from the commit messages
and prefixed by t/ by default; use '-p PREFIX' to specify
When mailing out your patch, basically only few extra headers
mail headers are inserted and the patch itself is appended.
Thus, as your patches evolve, you can record nuances like whether
When mailing out your patch, basically only few extra headers
mail headers are inserted and the patch itself is appended.
Thus, as your patches evolve, you can record nuances like whether
versa and similar nuances, if your project is into that.
From is prefilled from your current GIT_AUTHOR_IDENT, other headers
can be prefilled from various optional topgit.* config options.
versa and similar nuances, if your project is into that.
From is prefilled from your current GIT_AUTHOR_IDENT, other headers
can be prefilled from various optional topgit.* config options.