{"thread":{"id":"2743","subject":"[ANNOUNCE] GIT 0.99.9l aka 1.0rc4","startedAt":"2005-12-04T09:21:13Z","lastAt":"2005-12-07T16:20:30Z","messageCount":5,"participants":["Junio C Hamano","Gerrit Pape","Jon Loeliger"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"13174","messageId":"7vy831p69i.fsf@assigned-by-dhcp.cox.net","threadId":"2743","inReplyTo":null,"subject":"[ANNOUNCE] GIT 0.99.9l aka 1.0rc4","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-12-04T09:21:13Z","receivedAt":"2005-12-04T09:21:13Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"GIT 0.99.9l aka 1.0rc4 is found at a new location.\n\nRPM\n\thttp://kernel.org:/pub/software/git/RPMS/\n\nDebian [*1*]\n\thttp://kernel.org:/pub/software/git/debian/\n\nThis is mostly fixes, with some improvements.  As I said on the\ngit list earlier, no more major feature/semantics changes after\nthis is expected until 1.0.\n\nHighlights are:\n\n - After a conflicting merge, the index file is left unmerged.\n   As before, after such conflicting merge, \"git diff\" can be\n   used to view the differences between the half-merged file and\n   \"our\" branch version by default, but now you can say \"git\n   diff --base\" and \"git diff --theirs\" to view the differences\n   since the merge-base version and the other branch's version,\n   respectively.\n\n - git-daemon and other git native protocols allow user-relative\n   paths (e.g. git://host/~user/repo).  git-daemon's path\n   whitelist check used to be done with the realpath (i.e. what\n   getcwd() returns) in 0.99.9k and later \"master\" branch\n   versions, but it was changed back to check against what the\n   requester asked.\n\n - The commands have been future-proofed so that they refuse to\n   operate on repositories from future unknown versions, to\n   avoid corrupting them by mistake.\n\n - Bisect can take pathspec to cut down the number of revisions\n   that need to be tested.\n\n - Many low-level commands have been updated to work better from\n   subdirectories (much of the barebone porcelain wrappers that\n   deal with the whole repository or the whole tree still need\n   to be run from the top level, though).\n\n - Merge used to fail when it removed a file (fixed).\n\n - When only GIT_OBJECT_DIRECTORY was exported things broke\n   since 0.99.9k (fixed).\n\n - Comes with updated gitk.\n\n[Footnote]\n\n*1* It appears Debian finally has an official maintainer, so I\nam inclined to stop building and supplying the debs starting\nfrom the next version --- one less thing to worry about for me.\nI hope the Debian side splits the packages along the same line\nas we do RPMs.\n"},{"id":"13206","messageId":"20051205172601.4980.qmail@67565db8368c55.315fe32.mid.smarden.org","threadId":"2743","inReplyTo":"7vy831p69i.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 0.99.9l aka 1.0rc4","fromName":"Gerrit Pape","fromEmail":"pape@smarden.org","sentAt":"2005-12-05T17:26:01Z","receivedAt":"2005-12-05T17:26:01Z","isPatch":false,"sender":{"key":"pape@smarden.org","avatar":"https://avatars.githubusercontent.com/u/143170252?v=4"},"body":"On Sun, Dec 04, 2005 at 01:21:13AM -0800, Junio C Hamano wrote:\n> *1* It appears Debian finally has an official maintainer, so I\n\nYes, I've taken over maintainership, and introduced the git-core package\ninto Debian/unstable, the git tools previously were included in the\ncogito package.\n\n> am inclined to stop building and supplying the debs starting\n> from the next version --- one less thing to worry about for me.\n> I hope the Debian side splits the packages along the same line\n> as we do RPMs.\n\nI'll do so and split off git-arch, git-cvs, git-svn, git-email from the\ngit-core package, as already done with gitk.  Additionally I have the\nwebdocs in a separate git-doc package, maybe that's a good idea for the\nrpms also.\n\nRegards, Gerrit.\n"},{"id":"13212","messageId":"7vu0dnb8pm.fsf@assigned-by-dhcp.cox.net","threadId":"2743","inReplyTo":"20051205172601.4980.qmail@67565db8368c55.315fe32.mid.smarden.org","subject":"Re: [ANNOUNCE] GIT 0.99.9l aka 1.0rc4","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-12-05T20:16:37Z","receivedAt":"2005-12-05T20:16:37Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Gerrit Pape <pape@smarden.org> writes:\n\n> On Sun, Dec 04, 2005 at 01:21:13AM -0800, Junio C Hamano wrote:\n>> *1* It appears Debian finally has an official maintainer, so I\n>\n> Yes, I've taken over maintainership, and introduced the git-core package\n> into Debian/unstable, the git tools previously were included in the\n> cogito package.\n\nThis question is probably relevant only to you and people who\nwant to build deb themselves until you package the updated\nupstream, but what is your (and others') preference on debian/\ndirectory in what _I_ ship?\n\nI see three possibilities:\n\n - Do not care, and keep them as they are as they bitrot.\n\n - Remove debian/ from the upstream tree.\n\n - You feed patches to me, and I promise you not to touch\n   debian/ area, except adding a new -0 entry at the top of the\n   changelog when bumping the version number up, and perhaps\n   adjusting to the main Makefile changes if the solution is\n   obvious.\n\nI am neutral between the second and the third.\n"},{"id":"13222","messageId":"1133817028.8577.52.camel@cashmere.sps.mot.com","threadId":"2743","inReplyTo":"7vu0dnb8pm.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 0.99.9l aka 1.0rc4","fromName":"Jon Loeliger","fromEmail":"jdl@freescale.com","sentAt":"2005-12-05T21:10:29Z","receivedAt":"2005-12-05T21:10:29Z","isPatch":false,"sender":{"key":"jdl@jdl.com","avatar":"https://gravatar.com/avatar/75ce9a10b151acd2c28ec4ab2136dba7b2ff1634530bd04b155981a749d08a64?d=mp&s=160"},"body":"On Mon, 2005-12-05 at 14:16, Junio C Hamano wrote:\n\n> This question is probably relevant only to you and people who\n> want to build deb themselves until you package the updated\n> upstream, but what is your (and others') preference on debian/\n> directory in what _I_ ship?\n\nI would like to see it remain and be current, please.\n\nThanks,\njdl\n"},{"id":"13319","messageId":"20051207162030.18532.qmail@c9a97849515963.315fe32.mid.smarden.org","threadId":"2743","inReplyTo":"7vu0dnb8pm.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 0.99.9l aka 1.0rc4","fromName":"Gerrit Pape","fromEmail":"pape@smarden.org","sentAt":"2005-12-07T16:20:30Z","receivedAt":"2005-12-07T16:20:30Z","isPatch":false,"sender":{"key":"pape@smarden.org","avatar":"https://avatars.githubusercontent.com/u/143170252?v=4"},"body":"On Mon, Dec 05, 2005 at 12:16:37PM -0800, Junio C Hamano wrote:\n> Gerrit Pape <pape@smarden.org> writes:\n> > On Sun, Dec 04, 2005 at 01:21:13AM -0800, Junio C Hamano wrote:\n> >> *1* It appears Debian finally has an official maintainer, so I\n> >\n> > Yes, I've taken over maintainership, and introduced the git-core package\n> > into Debian/unstable, the git tools previously were included in the\n> > cogito package.\n> \n> This question is probably relevant only to you and people who\n> want to build deb themselves until you package the updated\n> upstream, but what is your (and others') preference on debian/\n> directory in what _I_ ship?\n> \n> I see three possibilities:\n> \n>  - Do not care, and keep them as they are as they bitrot.\n> \n>  - Remove debian/ from the upstream tree.\n> \n>  - You feed patches to me, and I promise you not to touch\n>    debian/ area, except adding a new -0 entry at the top of the\n>    changelog when bumping the version number up, and perhaps\n>    adjusting to the main Makefile changes if the solution is\n>    obvious.\n> \n> I am neutral between the second and the third.\n\nNormally we suggest upstream to not ship a debian/ directory at all, and\nI would prefer that.  But I can understand that people may got used to\nit, and prefer to build the packages on their own.  So I'm also fine\nwith feeding you with patches, but need to get 0.99.9l into the Debian\narchive first (already prepared, waiting in a 'new packages' queue), and\nthen adapt the build process to use the debian/ directory in the git\ntarball, instead of the current tarball-in-tarball approach.\n\nThis may take some days, and there are major changes to the debian/\ndirectory as I personally don't use the usual debhelper approach.\n\nThanks, Gerrit.\n"}]}