{"thread":{"id":"17566","subject":"What is not in git.git","startedAt":"2009-02-04T20:49:18Z","lastAt":"2009-02-05T14:02:15Z","messageCount":5,"participants":["Nanako Shiraishi","Junio C Hamano","Joey Hess","Ed Cashin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"103201","messageId":"20090205054918.6117@nanako3.lavabit.com","threadId":"17566","inReplyTo":null,"subject":"What is not in git.git","fromName":"Nanako Shiraishi","fromEmail":"nanako3@lavabit.com","sentAt":"2009-02-04T20:49:18Z","receivedAt":"2009-02-04T20:49:18Z","isPatch":false,"sender":{"key":"nanako3@lavabit.com","avatar":"https://gravatar.com/avatar/3777b9e201c5883a62b1a6fdf7c53f2d712d1d80989146063ea861e33aad72a8?d=mp&s=160"},"body":"You keep mentioning 1.6.2 and I take it as a hint that the project is\napproaching the pre release freeze. There are some patches sent to the\nlist that are not in git.git, and I am wondering what their statuses are.\n\n 1. From: ecashin@coraid.com\n Subject: [PATCH] git-describe documentation: --match pattern is glob\n Date: Thu, 22 Jan 2009 11:21:53 -0500\n Message-ID: \n\n I thought this was correct, but was missing a sign-off. Perhaps it was\n dropped on the floor because it was sent in a wrong format that is\n harder to apply?\n\n 2. From: Arjen Laarhoven \n Subject: [PATCH 2/2] git-log: Follow file copies with 'git log --follow -C -C'\n Date: Thu, 22 Jan 2009 17:37:25 +0100\n Message-ID: <1232642245-94405-2-git-send-email-arjen@yaph.org>\n\n Junio seemed to like the patch but asked a question; I did not see a\n response nor updated patch (sorry, I do not read C and cannot comment\n on the correctness of the patch).\n\n 3. From: Joey Hess \n Subject: [PATCH] gitweb: support the rel=vcs microformat\n Date: Tue, 6 Jan 2009 23:25:18 -0500\n Message-ID: <20090107042518.GB24735@gnu.kitenet.net>\n\n A few exchanges of review comments and responses, and then this topic\n went dark.\n\n From: Benjamin Kramer \n Subject: [PATCH] Makefile: Use libc strlcpy on OSX\n Date: Sat, 24 Jan 2009 16:41:30 +0100\n Message-ID: <7f978c810901240741k201f954dx1c0470186094ae24@mail.gmail.com>\n\n My reading of the thread is that the only remaining issue was to limit\n the change to specific versions, and I think people who use OSX can help\n polish this topic to completion.\n\n 4. From: Pete Wyckoff \n Subject: [PATCH] git-p4: avoid syncing duplicate changes\n Date: Wed, 28 Jan 2009 08:45:40 -0800\n Message-ID: <20090128164540.GA2137@padd.com>\n\n Nobody commented on this as far as I can tell. Do people not care\n about p4? Simon Hausmann seem to be the most recent active contributor\n and perhaps he can comment on this patch.\n\n 5. From: jidanni@jidanni.org\n Subject: [PATCH] Documentation/git-show-branch.txt: compact -g\n Date: Tue, 6 Jan 2009 11:14:02 +0800\n Message-Id: <1231211642-14463-1-git-send-email-jidanni@jidanni.org>\n\n I couldn't figure out what \"compact -g\" meant but other than that I\n think this patch is correct. Perhaps Junio has the author in his mail\n ignore list?\n\n 6. From: Alexander Potashev \n Subject: [PATCH] Replace deprecated dashed git commands in usage\n Date: Sun, 4 Jan 2009 21:39:27 +0300\n Message-ID: <1231094367-8831-1-git-send-email-aspotashev@gmail.com>\n\n This should have been in 1.6.0 already but it is still not.\n Forgotten?\n\n 7. From: Dirk Hörner \n Subject: [PATCH] git-cvsimport: add support for cvs pserver password scrambling.\n Date: Fri, 28 Nov 2008 20:06:40 +0200\n Message-ID: <5794AED2-43FF-4441-8292-0C9BFB3139A2@gmail.com>\n\n I think Johannes Schindelin commented but then nothing happened to\n this patch. Is there any more work necessary for its inclusion?\n\n 8. From: Heikki Hokkanen \n Subject: [PATCH] git show-ref: add --remotes option.\n Date: Mon, 13 Oct 2008 22:23:47 +0300\n Message-ID: <48F3A043.5070406@users.sf.net>\n\n I saw no comments but it is consistent with how git-rev-list allows\n you say branches and tags. Is there anything wrong with the patch?\n\n-- \nNanako Shiraishi\nhttp://ivory.ap.teacup.com/nanako3/\n"},{"id":"103222","messageId":"7vy6wllswz.fsf@gitster.siamese.dyndns.org","threadId":"17566","inReplyTo":"20090205054918.6117@nanako3.lavabit.com","subject":"Re: What is not in git.git","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-02-04T22:49:00Z","receivedAt":"2009-02-04T22:49:00Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nanako Shiraishi writes:\n\n> You keep mentioning 1.6.2 and I take it as a hint that the project is\n> approaching the pre release freeze. There are some patches sent to the\n> list that are not in git.git, and I am wondering what their statuses are.\n>\n> 1. From: ecashin@coraid.com\n> Subject: [PATCH] git-describe documentation: --match pattern is glob\n> Date: Thu, 22 Jan 2009 11:21:53 -0500\n> Message-ID: \n>\n> I thought this was correct, but was missing a sign-off. Perhaps it was\n> dropped on the floor because it was sent in a wrong format that is\n> harder to apply?\n\nMostly correct, but because we consider refnames like filesystem paths and\nthe use of globs when matching them is shared as the same basic design\nacross commands, I do not think the manual page for each individual\ncommand is the right place to say it.\n\n> 2. From: Arjen Laarhoven \n> Subject: [PATCH 2/2] git-log: Follow file copies with 'git log --follow -C -C'\n> Date: Thu, 22 Jan 2009 17:37:25 +0100\n> Message-ID: <1232642245-94405-2-git-send-email-arjen@yaph.org>\n>\n> Junio seemed to like the patch but asked a question; I did not see a\n> response nor updated patch (sorry, I do not read C and cannot comment\n> on the correctness of the patch).\n\nThanks for a reminder, and no, don't be sorry. This type of \"project\nsecretary\" help is very much appreciated, and you are demonstrating that\nyou do not have to know the code very intimately to do this, which is also\nvery good.\n\n> 3. From: Joey Hess \n> Subject: [PATCH] gitweb: support the rel=vcs microformat\n> Date: Tue, 6 Jan 2009 23:25:18 -0500\n> Message-ID: <20090107042518.GB24735@gnu.kitenet.net>\n>\n> A few exchanges of review comments and responses, and then this topic\n> went dark.\n\nThis is in \"The author will come back if he feels strongly enough, so I\ncan safely forget about it. I am not qualified to take over as the primary\npromoter of the topic if the author abandones it anyway\" (aka \"not mine\")\ncategory.\n\n> From: Benjamin Kramer \n> Subject: [PATCH] Makefile: Use libc strlcpy on OSX\n> Date: Sat, 24 Jan 2009 16:41:30 +0100\n> Message-ID: <7f978c810901240741k201f954dx1c0470186094ae24@mail.gmail.com>\n>\n> My reading of the thread is that the only remaining issue was to limit\n> the change to specific versions, and I think people who use OSX can help\n> polish this topic to completion.\n\nLikewise.\n\n> 4. From: Pete Wyckoff \n> Subject: [PATCH] git-p4: avoid syncing duplicate changes\n> Date: Wed, 28 Jan 2009 08:45:40 -0800\n> Message-ID: <20090128164540.GA2137@padd.com>\n>\n> Nobody commented on this as far as I can tell. Do people not care\n> about p4? Simon Hausmann seem to be the most recent active contributor\n> and perhaps he can comment on this patch.\n\nLikewise.\n\n> 5. From: jidanni@jidanni.org\n> Subject: [PATCH] Documentation/git-show-branch.txt: compact -g\n> Date: Tue, 6 Jan 2009 11:14:02 +0800\n> Message-Id: <1231211642-14463-1-git-send-email-jidanni@jidanni.org>\n>\n> I couldn't figure out what \"compact -g\" meant but other than that I\n> think this patch is correct. Perhaps Junio has the author in his mail\n> ignore list?\n\nI do not have anybody in my killfile. I think this patch is Ok with a\nminor fix to log as you say. How about\n\n\tgit-show-branch doc: show -g as synonym to --reflog in the list\n\n> 6. From: Alexander Potashev \n> Subject: [PATCH] Replace deprecated dashed git commands in usage\n> Date: Sun, 4 Jan 2009 21:39:27 +0300\n> Message-ID: <1231094367-8831-1-git-send-email-aspotashev@gmail.com>\n>\n> This should have been in 1.6.0 already but it is still not.\n> Forgotten?\n\nI haven't looked at it. As long as it only touches the messages and not\nstrings used to invoke other commands with their names, there shouldn't be\nany downside.\n\n> 7. From: Dirk Hörner \n> Subject: [PATCH] git-cvsimport: add support for cvs pserver password scrambling.\n> Date: Fri, 28 Nov 2008 20:06:40 +0200\n> Message-ID: <5794AED2-43FF-4441-8292-0C9BFB3139A2@gmail.com>\n>\n> I think Johannes Schindelin commented but then nothing happened to\n> this patch. Is there any more work necessary for its inclusion?\n\nAgain, this is in \"not mine\" category.\n\n> 8. From: Heikki Hokkanen \n> Subject: [PATCH] git show-ref: add --remotes option.\n> Date: Mon, 13 Oct 2008 22:23:47 +0300\n> Message-ID: <48F3A043.5070406@users.sf.net>\n>\n> I saw no comments but it is consistent with how git-rev-list allows\n> you say branches and tags. Is there anything wrong with the patch?\n\nHmm, ... goes to the archive ... I guess this shouldn't hurt.\n\nThanks. I wish there were more like you.\n"},{"id":"103226","messageId":"20090204230640.GA2924@gnu.kitenet.net","threadId":"17566","inReplyTo":"7vy6wllswz.fsf@gitster.siamese.dyndns.org","subject":"Re: What is not in git.git","fromName":"Joey Hess","fromEmail":"joey@kitenet.net","sentAt":"2009-02-04T23:06:40Z","receivedAt":"2009-02-04T23:06:40Z","isPatch":false,"sender":{"key":"joey@kitenet.net","avatar":"https://avatars.githubusercontent.com/u/16392?v=4"},"body":"Junio C Hamano wrote:\n> > 3. From: Joey Hess \n> > Subject: [PATCH] gitweb: support the rel=vcs microformat\n> > Date: Tue, 6 Jan 2009 23:25:18 -0500\n> > Message-ID: <20090107042518.GB24735@gnu.kitenet.net>\n> >\n> > A few exchanges of review comments and responses, and then this topic\n> > went dark.\n> \n> This is in \"The author will come back if he feels strongly enough, so I\n> can safely forget about it. I am not qualified to take over as the primary\n> promoter of the topic if the author abandones it anyway\" (aka \"not mine\")\n> category.\n\nIndeed. I've been meaning to get back to it and do a patch series\naddressing Jakub's feedback, but have not yet.\n \n-- \nsee shy jo\n"},{"id":"103236","messageId":"20090205083545.6117@nanako3.lavabit.com","threadId":"17566","inReplyTo":"7vy6wllswz.fsf@gitster.siamese.dyndns.org","subject":"Re: What is not in git.git","fromName":"Nanako Shiraishi","fromEmail":"nanako3@lavabit.com","sentAt":"2009-02-04T23:35:45Z","receivedAt":"2009-02-04T23:35:45Z","isPatch":false,"sender":{"key":"nanako3@lavabit.com","avatar":"https://gravatar.com/avatar/3777b9e201c5883a62b1a6fdf7c53f2d712d1d80989146063ea861e33aad72a8?d=mp&s=160"},"body":"Quoting Junio C Hamano writes:\n\n> Nanako Shiraishi writes:\n>\n>> 5. From: jidanni@jidanni.org\n>> Subject: [PATCH] Documentation/git-show-branch.txt: compact -g\n>> Date: Tue, 6 Jan 2009 11:14:02 +0800\n>> Message-Id: <1231211642-14463-1-git-send-email-jidanni@jidanni.org>\n>>\n>> I couldn't figure out what \"compact -g\" meant but other than that I\n>> think this patch is correct. Perhaps Junio has the author in his mail\n>> ignore list?\n>\n> I do not have anybody in my killfile. I think this patch is Ok with a\n> minor fix to log as you say. How about\n>\n> \tgit-show-branch doc: show -g as synonym to --reflog in the list\n\nThat is very readable.\n\n> Thanks. I wish there were more like you.\n\nYou're welcome.\n\n-- \nNanako Shiraishi\nhttp://ivory.ap.teacup.com/nanako3/\n"},{"id":"103335","messageId":"20090205140215.GB20348@coraid.com","threadId":"17566","inReplyTo":"7vy6wllswz.fsf@gitster.siamese.dyndns.org","subject":"Re: What is not in git.git","fromName":"Ed Cashin","fromEmail":"ecashin@coraid.com","sentAt":"2009-02-05T14:02:15Z","receivedAt":"2009-02-05T14:02:15Z","isPatch":false,"sender":{"key":"ecashin@coraid.com","avatar":null},"body":"On Wed, Feb 04, 2009 at 02:49:00PM -0800, Junio C Hamano wrote:\n> Nanako Shiraishi writes:\n...\n> > 1. From: ecashin@coraid.com\n> > Subject: [PATCH] git-describe documentation: --match pattern is glob\n> > Date: Thu, 22 Jan 2009 11:21:53 -0500\n> > Message-ID: \n> >\n> > I thought this was correct, but was missing a sign-off. Perhaps it was\n> > dropped on the floor because it was sent in a wrong format that is\n> > harder to apply?\n> \n> Mostly correct, but because we consider refnames like filesystem paths and\n> the use of globs when matching them is shared as the same basic design\n> across commands, I do not think the manual page for each individual\n> command is the right place to say it.\n\nI can add a sign-off if that would help, but it sounds like it was the\nwrong fix. I didn't know the right place to say it, but I figure: If\nthere is a right place, then what is it? If there isn't one, saying\nit in the git-describe manpage is probably a good step for now.\n\n-- \n Ed Cashin \n"}]}