{"thread":{"id":"15738","subject":"Re: [TG PATCH] README: Fix spelling and reflect recent depend support","startedAt":"2008-10-01T14:07:39Z","lastAt":"2008-10-01T15:17:21Z","messageCount":2,"participants":["Jonas Fonseca"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"299074","messageId":"1222870059-22077-1-git-send-email-fonseca@diku.dk","threadId":"15738","inReplyTo":null,"subject":"[TG PATCH] README: Fix spelling and reflect recent depend support","fromName":"Jonas Fonseca","fromEmail":"fonseca@diku.dk","sentAt":"2008-10-01T14:07:39Z","receivedAt":"2008-10-01T14:07:39Z","isPatch":true,"sender":{"key":"fonseca@diku.dk","avatar":"https://gravatar.com/avatar/f82f3ad698717c51873b020c750a92438c820a24056dc39fe4d07baa10a92264?d=mp&s=160"},"body":"Signed-off-by: Jonas Fonseca \n\n---\n README | 14 +++++++-------\n 1 files changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/README b/README\nindex 35a9f98..903face 100644\n--- a/README\n+++ b/README\n@@ -22,7 +22,7 @@ version control of patches (reordering of patches is not\n version-controlled at all). But there are several disadvantages -\n for one, these tools (especially StGIT) do not actually fit well\n with plain Git at all: it is basically impossible to take advantage\n-of the index efectively when using StGIT. But more importantly,\n+of the index effectively when using StGIT. But more importantly,\n these tools horribly fail in the face of distributed environment.\n \n TopGit has been designed around three main tenets:\n@@ -45,7 +45,7 @@ them.\n \n As mentioned above, the main intended use-case for TopGit is tracking\n third-party patches, where each patch is effectively a single topic\n-branch. In order to flexibly accomodate even complex scenarios when\n+branch. In order to flexibly accommodate even complex scenarios when\n you track many patches where many are independent but some depend\n on others, TopGit ignores the ancient Quilt heritage of patch series\n and instead allows the patches to freely form graphs (DAGs just like\n@@ -252,6 +252,7 @@ tg delete\n \tdepending on it.\n \n \tTODO: '-a' to delete all empty branches, depfix, revert\n+\tTODO: subcommand removing dependencies smoothly\n \n tg depend\n ~~~~~~~~~\n@@ -344,7 +345,7 @@ tg export\n \tin the cleaned up history (corresponding basically exactly\n \tto `tg patch` output for the topic branch).\n \n-\tThe command has two posible outputs now - either a Git branch\n+\tThe command has two possible outputs now - either a Git branch\n \twith the collapsed history, or a quilt series in new directory.\n \n \tIn case of producing collapsed history in new branch,\n@@ -449,7 +450,6 @@ tg update\n \n \tTODO: tg update -a for updating all topic branches\n \n-TODO: tg depend for adding/removing dependencies smoothly\n TODO: tg rename\n \n \n@@ -479,10 +479,10 @@ whatever Cc headers you choose or the post-three-dashes message.\n When mailing out your patch, basically only few extra headers\n mail headers are inserted and the patch itself is appended.\n Thus, as your patches evolve, you can record nuances like whether\n-the paricular patch should have To-list/Cc-maintainer or vice\n+the particular patch should have To-list/Cc-maintainer or vice\n versa and similar nuances, if your project is into that.\n-From is prefilled from your current GIT_AUTHOR_IDENT, other headers\n-can be prefilled from various optional topgit.* config options.\n+From is pre-filled from your current GIT_AUTHOR_IDENT, other headers\n+can be pre-filled from various optional topgit.* config options.\n \n \t.topdeps: Contains the one-per-line list of branches\n your patch depends on, pre-seeded with `tg create`. (Continuously\n-- \ntg: (67ae5b2..) jf/readme-update (depends on: master)\n"},{"id":"92060","messageId":"2c6b72b30810010817p1eff63b7r32d9fbd5b9223c3b@mail.gmail.com","threadId":"15738","inReplyTo":"1222870059-22077-1-git-send-email-fonseca@diku.dk","subject":"Re: [TG PATCH] README: Fix spelling and reflect recent depend support","fromName":"Jonas Fonseca","fromEmail":"fonseca@diku.dk","sentAt":"2008-10-01T15:17:21Z","receivedAt":"2008-10-01T15:17:21Z","isPatch":true,"sender":{"key":"fonseca@diku.dk","avatar":"https://gravatar.com/avatar/f82f3ad698717c51873b020c750a92438c820a24056dc39fe4d07baa10a92264?d=mp&s=160"},"body":"On Wed, Oct 1, 2008 at 16:07, Jonas Fonseca wrote:\n> Signed-off-by: Jonas Fonseca \n>\n> ---\n\nI have been trying to get `tg mail` to work and have a few questions.\nWould you mind if topgit didn't insert an empty line after the sob\nline? Most emails to this list doesn't have it. The patch mail I just\nsent had two 'To:' lines: one probably comes from topgit passing\ngit-send-email the --to option and the other comes from the patch file\n(basically .topmsg) containing a 'To:' line. Should `tg mail` be fixed\nto filter this somehow? Finally, tg-mail uses bash arrays, however,\nperhaps topgit could get away with just passing one --from and one\n--to option to git-send-email.\n\n> diff --git a/README b/README\n> index 35a9f98..903face 100644\n> --- a/README\n> +++ b/README\n> @@ -252,6 +252,7 @@ tg delete\n> depending on it.\n>\n> TODO: '-a' to delete all empty branches, depfix, revert\n> + TODO: subcommand removing dependencies smoothly\n>\n> tg depend\n> ~~~~~~~~~\n\nGah, this is obviously in the wrong subsection ...\n\n-- \nJonas Fonseca\n"}]}