{"thread":{"id":"29186","subject":"git-svn: multiple fetch lines","startedAt":"2011-12-16T19:51:19Z","lastAt":"2013-05-15T02:00:33Z","messageCount":11,"participants":["Nathan Gray","Jonathan Nieder","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"181329","messageId":"CA+7g9Jxd3mhbra34f+MiJRt36Lb6gVHi1nOCP8Zo5y-G9jB3qA@mail.gmail.com","threadId":"29186","inReplyTo":null,"subject":"git-svn: multiple fetch lines","fromName":"Nathan Gray","fromEmail":"n8gray@n8gray.org","sentAt":"2011-12-16T19:51:19Z","receivedAt":"2011-12-16T19:51:19Z","isPatch":false,"sender":{"key":"n8gray@n8gray.org","avatar":"https://avatars.githubusercontent.com/u/82794?v=4"},"body":"Hello,\n\nI'm in a conversation with the support fellow of the very nice Tower\ngit interface for OS X and we need clarification on a point. Does\ngit-svn explicitly support multiple \"fetch =\" lines in an svn-remote\nsection or is it just an accident that it works? My belief is that\nsuch support is intended and his is that it is accidental.\n\nYou can see a more detailed explanation of why you would want to use\nmultiple fetch lines on this fellow's blog post:\n\nhttp://davegoodell.blogspot.com/2009/04/multiple-remote-branches-in-git-svn.html\n\nMy company's svn server layout is a bit of a mess and to work around\nthat I've been using multiple \"fetch\" lines in git-svn's config:\n\n[svn-remote \"svn\"]\n url = https://...\n\n # The trunk\n fetch = foo/trunk/Product:refs/remotes/trunk\n\n # Some individual branches from messy directories that I can't use globs on\n fetch = foo/branches/Developers/Nathan/Project/Product:refs/remotes/product-orig\n fetch = foo/branches/august-demo/Product:refs/remotes/august-demo\n\n # A well-organized branches folder that I can use a glob for\n branches = foo/branches/Product/*:refs/remotes/branches/*\n\n # etc...\n\nTower doesn't currently support such configurations and I'd like to\nconvince them that this is a perfectly sensible thing to do.\n\nThanks,\n-Nathan\n\n-- \nHexaLex: A New Angle on Crossword Games for iPhone and iPod Touch\nhttp://hexalex.com\nOn The App Store: http://bit.ly/8Mj1CU\nOn Facebook: http://bit.ly/9MIJiV\nOn Twitter: http://twitter.com/hexalexgame\nhttp://n8gray.org\n"},{"id":"181381","messageId":"20111217100521.GA12610@elie.hsd1.il.comcast.net","threadId":"29186","inReplyTo":"CA+7g9Jxd3mhbra34f+MiJRt36Lb6gVHi1nOCP8Zo5y-G9jB3qA@mail.gmail.com","subject":"Re: git-svn: multiple fetch lines","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-12-17T10:05:21Z","receivedAt":"2011-12-17T10:05:21Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi Nathan,\n\nNathan Gray wrote:\n\n> I'm in a conversation with the support fellow of the very nice Tower\n> git interface for OS X and we need clarification on a point. Does\n> git-svn explicitly support multiple \"fetch =\" lines in an svn-remote\n> section or is it just an accident that it works? My belief is that\n> such support is intended and his is that it is accidental.\n\nIt's true that the documentation is not as clear about this as one\nmight like. Documentation/git-svn.txt leaves it to the reader to\ninfer that this is supported by analogy with \"fetch =\" lines in native\ngit [remote] sections:\n\n\t'git svn' stores [svn-remote] configuration information in the\n\trepository .git/config file. It is similar the core git\n\t[remote] sections except 'fetch' keys do not accept glob\n\targuments; but they are instead handled by the 'branches'\n\tand 'tags' keys.\n\nThe change description for the patch that introduced that functionality\nis more helpful.\n\n\t$ git log -S'Could not find a \\\"svn-remote.*.fetch\\\" key' git-svn.perl\n\tcommit 706587fc\n\tAuthor: Eric Wong \n\tDate: Thu Jan 18 17:50:01 2007 -0800\n\n\t git-svn: add support for metadata in .git/config\n\t \n\t Of course, we handle metadata migrations from previous versions\n\t and we have added unit tests.\n\t \n\t The new .git/config remotes resemble non-SVN remotes. Below\n\t is an example with comments:\n[example using multiple 'fetch' keys snipped]\n\nPerhaps such an example would be useful for the git-svn(1) manpage,\ntoo. Any ideas for where to add such a note, and how it should be\nworded? (Of course, if you can phrase such an idea in patch form,\nthat would be the most convenient.)\n\nHope that helps,\nJonathan\n"},{"id":"181492","messageId":"CA+7g9JzatFYViMk302uU-X=YQGF2wEsmASkLPm0tDfQvpL_-vQ@mail.gmail.com","threadId":"29186","inReplyTo":"20111217100521.GA12610@elie.hsd1.il.comcast.net","subject":"Re: git-svn: multiple fetch lines","fromName":"Nathan Gray","fromEmail":"n8gray@n8gray.org","sentAt":"2011-12-19T21:40:50Z","receivedAt":"2011-12-19T21:40:50Z","isPatch":false,"sender":{"key":"n8gray@n8gray.org","avatar":"https://avatars.githubusercontent.com/u/82794?v=4"},"body":"Hi,\n\nOn Sat, Dec 17, 2011 at 2:05 AM, Jonathan Nieder wrote:\n> Hi Nathan,\n>\n> Nathan Gray wrote:\n>\n>> I'm in a conversation with the support fellow of the very nice Tower\n>> git interface for OS X and we need clarification on a point.  Does\n>> git-svn explicitly support multiple \"fetch =\" lines in an svn-remote\n>> section or is it just an accident that it works?  My belief is that\n>> such support is intended and his is that it is accidental.\n>\n> It's true that the documentation is not as clear about this as one\n> might like.  Documentation/git-svn.txt leaves it to the reader to\n> infer that this is supported by analogy with \"fetch =\" lines in native\n> git [remote] sections:\n\nThanks Jonathan, that's just what I suspected.\n\n[snip]\n\n> Perhaps such an example would be useful for the git-svn(1) manpage,\n> too.  Any ideas for where to add such a note, and how it should be\n> worded?  (Of course, if you can phrase such an idea in patch form,\n> that would be the most convenient.)\n\nThe existing CONFIGURATION section of the man page seems like a\nsensible place to mention multiple fetch entries. I've also found the\ndocumentation on creating branches in the presence of multiple branch\nkeys to be confusing and in need of an example, so maybe that could go\nin as well. How about something along these lines:\n\n\"\"\"\nIn order to simplify working with messy subversion repositories you\ncan configure multiple fetch, branches, and tags keys. For example:\n\n[svn-remote \"messy-repo\"]\n url = http://server.org/svn\n fetch = trunk/project-a:refs/remotes/project-a/trunk\n fetch = branches/demos/june-project-a-demo:refs/remotes/project-a/demos/june-demo\n branches = branches/server/*:refs/remotes/project-a/branches/*\n branches = branches/demos/2011/*:refs/remotes/project-a/2011-demos/*\n tags = tags/server/*:refs/remotes/project-a/tags/*\n\nTo create a branch in this configuration you need to specify the\nlocation for the new branch using the -d or --destination flag. For\nexample:\n\ngit svn branch -d wtf-goes-here-anyway?? release-2-3-0\n\"\"\"\n\nThe thing about the -d option that confuses me is that I'm not sure if\nI'm supposed to be supplying a full svn path, a partial svn path, the\nglob from the config file, etc. An example would make it obvious.\nPersonally, I always take the coward's way out and comment out the\nextra branches keys, make the branch without -d, then restore them in\norder to avoid any potential problems. :^)\n\nThanks,\n-Nathan\n\n-- \nHexaLex: A New Angle on Crossword Games for iPhone and iPod Touch\nhttp://hexalex.com\nOn The App Store: http://bit.ly/8Mj1CU\nOn Facebook: http://bit.ly/9MIJiV\nOn Twitter: http://twitter.com/hexalexgame\nhttp://n8gray.org\n"},{"id":"181505","messageId":"20111220012236.GB20979@elie.hsd1.il.comcast.net","threadId":"29186","inReplyTo":"CA+7g9JzatFYViMk302uU-X=YQGF2wEsmASkLPm0tDfQvpL_-vQ@mail.gmail.com","subject":"[RFC/PATCH 0/2] Re: git-svn: multiple fetch lines","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-12-20T01:22:36Z","receivedAt":"2011-12-20T01:22:36Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Nathan Gray wrote:\n\n> How about something along these lines:\n\nSounds sensible. Here's a patch series along those lines to get\nthings started. Please feel free to try them (use \"make -C\nDocumentation git-svn.1\" to test), tweak to taste, and resend when\nready for Eric to pick up.\n\nThanks,\n\nJonathan Nieder (1):\n git-svn: clarify explanation of --destination argument\n\nNathan Gray (1):\n git-svn: multiple fetch/branches/tags keys are supported\n\n Documentation/git-svn.txt | 31 ++++++++++++++++++++++++++-----\n 1 files changed, 26 insertions(+), 5 deletions(-)\n"},{"id":"181506","messageId":"20111220012350.GC20979@elie.hsd1.il.comcast.net","threadId":"29186","inReplyTo":"20111220012236.GB20979@elie.hsd1.il.comcast.net","subject":"[PATCH 1/2] git-svn: multiple fetch/branches/tags keys are supported","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-12-20T01:23:50Z","receivedAt":"2011-12-20T01:23:50Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"From: Nathan Gray \n\n\"git svn\" can be configured to use multiple fetch, branches, and tags\nrefspecs by passing multiple --branches or --tags options at init time\nor editing the configuration file later, which can be handy when\nworking with messy Subversion repositories. Add a note to the\nconfiguration section documenting how this works.\n\nSigned-off-by: Jonathan Nieder \n---\n Documentation/git-svn.txt | 12 ++++++++++++\n 1 files changed, 12 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex 34ee7850..66fd60a4 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -923,6 +923,18 @@ comma-separated list of names within braces. For example:\n \ttags = tags/{1.0,2.0}/src:refs/remotes/tags/*\n ------------------------------------------------------------------------\n \n+Multiple fetch, branches, and tags keys are supported:\n+\n+------------------------------------------------------------------------\n+[svn-remote \"messy-repo\"]\n+\turl = http://server.org/svn\n+\tfetch = trunk/project-a:refs/remotes/project-a/trunk\n+\tfetch = branches/demos/june-project-a-demo:refs/remotes/project-a/demos/june-demo\n+\tbranches = branches/server/*:refs/remotes/project-a/branches/*\n+\tbranches = branches/demos/2011/*:refs/remotes/project-a/2011-demos/*\n+\ttags = tags/server/*:refs/remotes/project-a/tags/*\n+------------------------------------------------------------------------\n+\n Note that git-svn keeps track of the highest revision in which a branch\n or tag has appeared. If the subset of branches or tags is changed after\n fetching, then .git/svn/.metadata must be manually edited to remove (or\n-- \n1.7.8\n"},{"id":"181507","messageId":"20111220012430.GD20979@elie.hsd1.il.comcast.net","threadId":"29186","inReplyTo":"20111220012236.GB20979@elie.hsd1.il.comcast.net","subject":"[PATCH 2/2] git-svn: clarify explanation of --destination argument","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-12-20T01:24:30Z","receivedAt":"2011-12-20T01:24:30Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"The existing documentation for \"-d\" does not make it obvious whether\nits argument is supposed to be a full svn path, a partial svn path,\nthe glob from the config file, or what. Clarify the text and add an\nexample to get the reader started.\n\nReported-by: Nathan Gray \nSigned-off-by: Jonathan Nieder \n---\n Documentation/git-svn.txt | 19 ++++++++++++++-----\n 1 files changed, 14 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex 66fd60a4..a343c261 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -254,13 +254,15 @@ first have already been pushed into SVN.\n \tCreate a tag by using the tags_subdir instead of the branches_subdir\n \tspecified during git svn init.\n \n--d;;\n---destination;;\n+-d;;\n+--destination=;;\n+\n \tIf more than one --branches (or --tags) option was given to the 'init'\n \tor 'clone' command, you must provide the location of the branch (or\n-\ttag) you wish to create in the SVN repository. The value of this\n-\toption must match one of the paths specified by a --branches (or\n-\t--tags) option. You can see these paths with the commands\n+\ttag) you wish to create in the SVN repository. specifies which\n+\tpath to use to create the branch or tag and should match the pattern\n+\ton the left-hand side of one of the configured branches or tags\n+\trefspecs. You can see these refspecs with the commands\n +\n \tgit config --get-all svn-remote..branches\n \tgit config --get-all svn-remote..tags\n@@ -935,6 +937,13 @@ Multiple fetch, branches, and tags keys are supported:\n \ttags = tags/server/*:refs/remotes/project-a/tags/*\n ------------------------------------------------------------------------\n \n+Creating a branch in such a configuration requires disambiguating which\n+location to use using the -d or --destination flag:\n+\n+------------------------------------------------------------------------\n+$ git svn branch -d branches/server release-2-3-0\n+------------------------------------------------------------------------\n+\n Note that git-svn keeps track of the highest revision in which a branch\n or tag has appeared. If the subset of branches or tags is changed after\n fetching, then .git/svn/.metadata must be manually edited to remove (or\n-- \n1.7.8\n"},{"id":"181514","messageId":"CA+7g9JyJC77ETez-wrOPRPxdY+0nbwohkR_vP=Tt3bjw-XhHaQ@mail.gmail.com","threadId":"29186","inReplyTo":"20111220012350.GC20979@elie.hsd1.il.comcast.net","subject":"Re: [PATCH 1/2] git-svn: multiple fetch/branches/tags keys are supported","fromName":"Nathan Gray","fromEmail":"n8gray@n8gray.org","sentAt":"2011-12-20T06:42:20Z","receivedAt":"2011-12-20T06:42:20Z","isPatch":true,"sender":{"key":"n8gray@n8gray.org","avatar":"https://avatars.githubusercontent.com/u/82794?v=4"},"body":"Looks good! These doc changes will help a lot.\n\nThanks,\n-Nathan\n\nOn Mon, Dec 19, 2011 at 5:23 PM, Jonathan Nieder wrote:\n> From: Nathan Gray \n>\n> \"git svn\" can be configured to use multiple fetch, branches, and tags\n> refspecs by passing multiple --branches or --tags options at init time\n> or editing the configuration file later, which can be handy when\n> working with messy Subversion repositories.  Add a note to the\n> configuration section documenting how this works.\n>\n> Signed-off-by: Jonathan Nieder \n> ---\n>  Documentation/git-svn.txt |   12 ++++++++++++\n>  1 files changed, 12 insertions(+), 0 deletions(-)\n>\n> diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\n> index 34ee7850..66fd60a4 100644\n> --- a/Documentation/git-svn.txt\n> +++ b/Documentation/git-svn.txt\n> @@ -923,6 +923,18 @@ comma-separated list of names within braces. For example:\n>        tags = tags/{1.0,2.0}/src:refs/remotes/tags/*\n>  ------------------------------------------------------------------------\n>\n> +Multiple fetch, branches, and tags keys are supported:\n> +\n> +------------------------------------------------------------------------\n> +[svn-remote \"messy-repo\"]\n> +       url = http://server.org/svn\n> +       fetch = trunk/project-a:refs/remotes/project-a/trunk\n> +       fetch = branches/demos/june-project-a-demo:refs/remotes/project-a/demos/june-demo\n> +       branches = branches/server/*:refs/remotes/project-a/branches/*\n> +       branches = branches/demos/2011/*:refs/remotes/project-a/2011-demos/*\n> +       tags = tags/server/*:refs/remotes/project-a/tags/*\n> +------------------------------------------------------------------------\n> +\n>  Note that git-svn keeps track of the highest revision in which a branch\n>  or tag has appeared. If the subset of branches or tags is changed after\n>  fetching, then .git/svn/.metadata must be manually edited to remove (or\n> --\n> 1.7.8\n>\n\n\n\n-- \nHexaLex: A New Angle on Crossword Games for iPhone and iPod Touch\nhttp://hexalex.com\nOn The App Store: http://bit.ly/8Mj1CU\nOn Facebook: http://bit.ly/9MIJiV\nOn Twitter: http://twitter.com/hexalexgame\nhttp://n8gray.org\n"},{"id":"217238","messageId":"20130513213055.GE3657@google.com","threadId":"29186","inReplyTo":"20111220012236.GB20979@elie.hsd1.il.comcast.net","subject":"[PATCH resend 0/2] git-svn: improve documentation of multiple fetch lines","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2013-05-13T21:30:55Z","receivedAt":"2013-05-13T21:30:55Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi Eric,\n\nI last sent these patches as an RFC a year and a half or so ago[1].\nNathan seemed to like them and they still seem valid, so thought\nI'd resubmit. :)\n\nThoughts of all kinds welcome, as always.\n\nJonathan Nieder (1):\n git-svn: clarify explanation of --destination argument\n\nNathan Gray (1):\n git-svn: multiple fetch/branches/tags keys are supported\n\n Documentation/git-svn.txt | 31 ++++++++++++++++++++++++++-----\n 1 file changed, 26 insertions(+), 5 deletions(-)\n\n[1] http://thread.gmane.org/gmane.comp.version-control.git/187312/focus=187489\n"},{"id":"217239","messageId":"20130513213131.GF3657@google.com","threadId":"29186","inReplyTo":"20130513213055.GE3657@google.com","subject":"[PATCH 1/2] git-svn: multiple fetch/branches/tags keys are supported","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2013-05-13T21:31:31Z","receivedAt":"2013-05-13T21:31:31Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"From: Nathan Gray \nDate: Mon, 19 Dec 2011 19:23:50 -0600\n\n\"git svn\" can be configured to use multiple fetch, branches, and tags\nrefspecs by passing multiple --branches or --tags options at init time\nor editing the configuration file later, which can be handy when\nworking with messy Subversion repositories. Add a note to the\nconfiguration section documenting how this works.\n\nSigned-off-by: Jonathan Nieder \n---\nAs before.\n\n Documentation/git-svn.txt | 12 ++++++++++++\n 1 file changed, 12 insertions(+)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex 58b6d54..6c0988e 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -1032,6 +1032,18 @@ comma-separated list of names within braces. For example:\n \ttags = tags/{1.0,2.0}/src:refs/remotes/tags/*\n ------------------------------------------------------------------------\n \n+Multiple fetch, branches, and tags keys are supported:\n+\n+------------------------------------------------------------------------\n+[svn-remote \"messy-repo\"]\n+\turl = http://server.org/svn\n+\tfetch = trunk/project-a:refs/remotes/project-a/trunk\n+\tfetch = branches/demos/june-project-a-demo:refs/remotes/project-a/demos/june-demo\n+\tbranches = branches/server/*:refs/remotes/project-a/branches/*\n+\tbranches = branches/demos/2011/*:refs/remotes/project-a/2011-demos/*\n+\ttags = tags/server/*:refs/remotes/project-a/tags/*\n+------------------------------------------------------------------------\n+\n Note that git-svn keeps track of the highest revision in which a branch\n or tag has appeared. If the subset of branches or tags is changed after\n fetching, then .git/svn/.metadata must be manually edited to remove (or\n-- \n1.8.3.rc1\n"},{"id":"217240","messageId":"20130513213234.GG3657@google.com","threadId":"29186","inReplyTo":"20130513213055.GE3657@google.com","subject":"[PATCH 2/2] git-svn: clarify explanation of --destination argument","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2013-05-13T21:32:34Z","receivedAt":"2013-05-13T21:32:34Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Date: Mon, 19 Dec 2011 19:24:30 -0600\n\nThe existing documentation for \"-d\" does not make it obvious whether\nits argument is supposed to be a full svn path, a partial svn path,\nthe glob from the config file, or what. Clarify the text and add an\nexample to get the reader started.\n\nReported-by: Nathan Gray \nSigned-off-by: Jonathan Nieder \n---\nThanks for reading.\n\n Documentation/git-svn.txt | 19 ++++++++++++++-----\n 1 file changed, 14 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex 6c0988e..68c706d 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -271,13 +271,15 @@ first have already been pushed into SVN.\n \tCreate a tag by using the tags_subdir instead of the branches_subdir\n \tspecified during git svn init.\n \n--d;;\n---destination;;\n+-d;;\n+--destination=;;\n+\n \tIf more than one --branches (or --tags) option was given to the 'init'\n \tor 'clone' command, you must provide the location of the branch (or\n-\ttag) you wish to create in the SVN repository. The value of this\n-\toption must match one of the paths specified by a --branches (or\n-\t--tags) option. You can see these paths with the commands\n+\ttag) you wish to create in the SVN repository. specifies which\n+\tpath to use to create the branch or tag and should match the pattern\n+\ton the left-hand side of one of the configured branches or tags\n+\trefspecs. You can see these refspecs with the commands\n +\n \tgit config --get-all svn-remote..branches\n \tgit config --get-all svn-remote..tags\n@@ -1044,6 +1046,13 @@ Multiple fetch, branches, and tags keys are supported:\n \ttags = tags/server/*:refs/remotes/project-a/tags/*\n ------------------------------------------------------------------------\n \n+Creating a branch in such a configuration requires disambiguating which\n+location to use using the -d or --destination flag:\n+\n+------------------------------------------------------------------------\n+$ git svn branch -d branches/server release-2-3-0\n+------------------------------------------------------------------------\n+\n Note that git-svn keeps track of the highest revision in which a branch\n or tag has appeared. If the subset of branches or tags is changed after\n fetching, then .git/svn/.metadata must be manually edited to remove (or\n-- \n1.8.3.rc1\n"},{"id":"217404","messageId":"20130515020033.GA23703@dcvr.yhbt.net","threadId":"29186","inReplyTo":"20130513213055.GE3657@google.com","subject":"Re: [PATCH resend 0/2] git-svn: improve documentation of multiple fetch lines","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2013-05-15T02:00:33Z","receivedAt":"2013-05-15T02:00:33Z","isPatch":true,"sender":{"key":"e@80x24.org","avatar":null},"body":"Jonathan Nieder wrote:\n> I last sent these patches as an RFC a year and a half or so ago[1].\n> Nathan seemed to like them and they still seem valid, so thought\n> I'd resubmit. :)\n\nThanks, both applied. Sorry for forgetting :x\n"}]}