{"thread":{"id":"8111","subject":"[PATCH 0/3] Remotes library, take 4","startedAt":"2007-05-12T15:45:48Z","lastAt":"2007-05-12T19:37:30Z","messageCount":3,"participants":["Daniel Barkalow","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":3},"messages":[{"id":"41931","messageId":"Pine.LNX.4.64.0705121137400.18541@iabervon.org","threadId":"8111","inReplyTo":null,"subject":"[PATCH 0/3] Remotes library, take 4","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-05-12T15:45:48Z","receivedAt":"2007-05-12T15:45:48Z","isPatch":true,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"Updated for recent review. If remote section name starts with '/', it is \nignored (like in 1.5.0). If a remote section option has no value, it is \nalso ignored (so it doesn't crash, and to be forward-compatible if we \nintroduce a boolean option later).\n\nThe struct refspec field and associated variables are spelled \"dst\".\n\nPart 3 is unchanged.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"41950","messageId":"7vfy61zvtx.fsf@assigned-by-dhcp.cox.net","threadId":"8111","inReplyTo":"Pine.LNX.4.64.0705121137400.18541@iabervon.org","subject":"Re: [PATCH 0/3] Remotes library, take 4","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-05-12T19:27:22Z","receivedAt":"2007-05-12T19:27:22Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Daniel Barkalow <barkalow@iabervon.org> writes:\n\n> Updated for recent review. If remote section name starts with '/', it is \n> ignored (like in 1.5.0). If a remote section option has no value, it is \n> also ignored (so it doesn't crash, and to be forward-compatible if we \n> introduce a boolean option later).\n>\n> The struct refspec field and associated variables are spelled \"dst\".\n>\n> Part 3 is unchanged.\n\nIt cannot be left unchanged as it is affected by the dest stuff.\n\nI'll push out a fixed-up one on 'pu' soonish.  Let's stabilize\nthis a bit without too many resends.\n"},{"id":"41960","messageId":"Pine.LNX.4.64.0705121531480.18541@iabervon.org","threadId":"8111","inReplyTo":"7vfy61zvtx.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH 0/3] Remotes library, take 4","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-05-12T19:37:30Z","receivedAt":"2007-05-12T19:37:30Z","isPatch":true,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Sat, 12 May 2007, Junio C Hamano wrote:\n\n> Daniel Barkalow <barkalow@iabervon.org> writes:\n> \n> > Updated for recent review. If remote section name starts with '/', it is \n> > ignored (like in 1.5.0). If a remote section option has no value, it is \n> > also ignored (so it doesn't crash, and to be forward-compatible if we \n> > introduce a boolean option later).\n> >\n> > The struct refspec field and associated variables are spelled \"dst\".\n> >\n> > Part 3 is unchanged.\n> \n> It cannot be left unchanged as it is affected by the dest stuff.\n> \n> I'll push out a fixed-up one on 'pu' soonish.  Let's stabilize\n> this a bit without too many resends.\n\nYeah, I think we agree on how it should be now, and I'm just confusing \nmyself regenerating patches. Although, possibly, the comment about NULL \nvalue should go into documentation for config_fn_t instead, since it's of \nmore general applicability than just this.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}