{"thread":{"id":"32815","subject":"Getting started contributing.","startedAt":"2013-02-03T06:21:48Z","lastAt":"2013-02-04T13:37:46Z","messageCount":9,"participants":["adamfraser","Junio C Hamano","Duy Nguyen","Philip Oakley","Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"208535","messageId":"1359872508519-7576834.post@n2.nabble.com","threadId":"32815","inReplyTo":null,"subject":"Getting started contributing.","fromName":"adamfraser","fromEmail":"adamfraser0@gmail.com","sentAt":"2013-02-03T06:21:48Z","receivedAt":"2013-02-03T06:21:48Z","isPatch":false,"sender":{"key":"adamfraser0@gmail.com","avatar":null},"body":"Hi, \nI would like to start contributing to git and am looking for a small project\nidea to get started with. On the Small Project Ideas wiki\n site there is a\nsuggestion for adding a 'git rebase --status' command that sounds like it\nwould be good for someone who has little knowledge of the code base. Is this\nproject still wanted? Aside from that, I've done a little searching and\nhaven't been able to find an official bug tracker for git is there somewhere\nI can find some bugs to help fix?\nApologies if this isn't the correct place to be posting.\nThanks\nAdam Fraser\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/Getting-started-contributing-tp7576834.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"208536","messageId":"7vhaltalre.fsf@alter.siamese.dyndns.org","threadId":"32815","inReplyTo":"1359872508519-7576834.post@n2.nabble.com","subject":"Re: Getting started contributing.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-02-03T07:40:05Z","receivedAt":"2013-02-03T07:40:05Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"adamfraser writes:\n\n> I would like to start contributing to git and am looking for a small project\n> idea to get started with. On the Small Project Ideas wiki\n> site there is a\n> suggestion for adding a 'git rebase --status' command that sounds like it\n> would be good for someone who has little knowledge of the code base.\n\nI think the two patches Duy just posted tonight overlap with that\ntopic, and I suspect it would give the end users a better experience\nto put the information in \"git status\" output rather than a separate\n\"git rebase\" subcommand. Perhaps you can work with him to see what\nother things his patch may have missed can be improved?\n"},{"id":"208537","messageId":"7vd2whalax.fsf@alter.siamese.dyndns.org","threadId":"32815","inReplyTo":"1359872508519-7576834.post@n2.nabble.com","subject":"Re: Getting started contributing.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-02-03T07:49:58Z","receivedAt":"2013-02-03T07:49:58Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"adamfraser writes:\n\n> I've done a little searching and\n> haven't been able to find an official bug tracker for git is there somewhere\n> I can find some bugs to help fix?\n\nYou came to the right place. A new bug or regression is reported to\nthis list, and it often is fixed (or often diagnosed as pebcak)\nfairly quickly by list regulars. Nobody maintains a bugzilla that\nis not maintained and is full of stale/invalid bug reports.\n\nThe best contribution a new person can make is to use the software\nregularly and find issues. It is very hard to find real bugs that\ncan easily be fixed by somebody totally new to the codebase in Git\nthese days.\n\nOn the other hand, there probably still are many loose ends. When a\ncommand is supposed to take only two arguments because taking more\nthan three does not make any sense, for example, it has not been\nunusual for us to document the two-argument form of the command,\nreject if the user gives only one argument with an error message,\nbut we simply ignore the third argument if the user mistakenly runs\nthe command with three arguments, instead of erroring out (i.e. the\ncode does not bother to help insane or too inexperienced users).\nThat kind of things are hard to find by users experienced with Git\nexactly because they know running such a command with three or more\narguments is nonsense, and they do not even try to make such a\nmistake. Still, it would be very nice to find and fix such issues.\n\nThanks.\n"},{"id":"208538","messageId":"CACsJy8AYOAwLKufQ34brk1agyFAX9xjgAE9_LAcRx=RGxcEZzg@mail.gmail.com","threadId":"32815","inReplyTo":"7vd2whalax.fsf@alter.siamese.dyndns.org","subject":"Re: Getting started contributing.","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2013-02-03T09:54:57Z","receivedAt":"2013-02-03T09:54:57Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Sun, Feb 3, 2013 at 2:49 PM, Junio C Hamano wrote:\n> On the other hand, there probably still are many loose ends.\n\nA few other things\n\n - Mark more strings for translation (not as easy as it sounds, some\nstrings can't be translated)\n - Color more in the output where it makes sense\n - Stop/Warn the user from updating HEAD (e.g. checkout another\nbranch) while in the middle of a rebase (some makes sense, most is by\nmistake)\n\nPS. You are welcome to improve my two patches Junio mentioned. I don't\nthink it overlaps much with \"git rebase --status\" though. Printing the\nremaining steps, or what patch being applied is not going to be done\nby \"git status\".\n-- \nDuy\n"},{"id":"208541","messageId":"77A6ABB842334FFFA04970DEAFAB6D0D@PhilipOakley","threadId":"32815","inReplyTo":"7vd2whalax.fsf@alter.siamese.dyndns.org","subject":"Re: Getting started contributing.","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":null,"receivedAt":"2013-02-03T13:02:37Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Junio C Hamano\" \nSent: Sunday, February 03, 2013 7:49 AM\n> adamfraser writes:\n>\n>> I've done a little searching and\n>> haven't been able to find an official bug tracker for git is there \n>> somewhere\n>> I can find some bugs to help fix?\n>\n> You came to the right place. A new bug or regression is reported to\n> this list, and it often is fixed (or often diagnosed as pebcak)\n> fairly quickly by list regulars. Nobody maintains a bugzilla that\n> is not maintained and is full of stale/invalid bug reports.\n>\n> The best contribution a new person can make is to use the software\n> regularly and find issues. It is very hard to find real bugs that\n> can easily be fixed by somebody totally new to the codebase in Git\n> these days.\n>\n> On the other hand, there probably still are many loose ends. When a\n> command is supposed to take only two arguments because taking more\n> than three does not make any sense, for example, it has not been\n> unusual for us to document the two-argument form of the command,\n> reject if the user gives only one argument with an error message,\n> but we simply ignore the third argument if the user mistakenly runs\n> the command with three arguments, instead of erroring out (i.e. the\n> code does not bother to help insane or too inexperienced users).\n> That kind of things are hard to find by users experienced with Git\n> exactly because they know running such a command with three or more\n> arguments is nonsense, and they do not even try to make such a\n> mistake. Still, it would be very nice to find and fix such issues.\n>\nA review of the git-user list \nhttps://groups.google.com/forum/?fromgroups#!forum/git-users is one \nplace to discover some of the user issues and thinking about how to \naddress them. Or resurrect issues from this Git list. E.g. There are a \nnumber of sub-module improvements available there.\n\nIf you have any Windows experience the MSysGit team \nhttps://github.com/msysgit/msysgit is always looking for help on some of \nthe compatibility issues, e.g. where the Linux optimisations conflict \nwith the Windows approaches.\n\nAnother area is picking out documentation issues you have seen and \nsubmitting patches for them, whether in the command man pages or in the \nguides. On my 'todo' list is to make the `help` command actually list \nthe \"Help me\" (i.e. guides and articles) pages, not just the command man \npages.\n\nI also had -\n* Bulk move detection (when folk change/move upper level directory \nnames).\n* add a .gitnevermerge option to stop private files you don't want in \n'master' (or any other branch) to be merged\n\nPhilip\n"},{"id":"208559","messageId":"7v1ucx9o4m.fsf@alter.siamese.dyndns.org","threadId":"32815","inReplyTo":"CACsJy8AYOAwLKufQ34brk1agyFAX9xjgAE9_LAcRx=RGxcEZzg@mail.gmail.com","subject":"Re: Getting started contributing.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-02-03T19:46:33Z","receivedAt":"2013-02-03T19:46:33Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Duy Nguyen writes:\n\n> On Sun, Feb 3, 2013 at 2:49 PM, Junio C Hamano wrote:\n>> On the other hand, there probably still are many loose ends.\n>\n> A few other things\n>\n> - Mark more strings for translation (not as easy as it sounds, some\n> strings can't be translated)\n\nTrue, but not a good advice for somebody new, exactly for the reason\nyou stated, i.e. some strings must not be translated.\n\n> - Color more in the output where it makes sense\n\nEeek.\n\n> - Stop/Warn the user from updating HEAD (e.g. checkout another\n> branch) while in the middle of a rebase (some makes sense, most is by\n> mistake)\n\nPerhaps, but again probably not for somebody new who hasn't mastered\nvarious workflows and understood why it may make sense to allow it.\n"},{"id":"208596","messageId":"1359967349302-7576901.post@n2.nabble.com","threadId":"32815","inReplyTo":"7v1ucx9o4m.fsf@alter.siamese.dyndns.org","subject":"Re: Getting started contributing.","fromName":"adamfraser","fromEmail":"adamfraser0@gmail.com","sentAt":"2013-02-04T08:42:29Z","receivedAt":"2013-02-04T08:42:29Z","isPatch":false,"sender":{"key":"adamfraser0@gmail.com","avatar":null},"body":"Thanks for all of the replies. I'll have a look into the suggestions and try\nto find somewhere I can help out. :)\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/Getting-started-contributing-tp7576834p7576901.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"208609","messageId":"vpqk3qomd2m.fsf@grenoble-inp.fr","threadId":"32815","inReplyTo":"1359872508519-7576834.post@n2.nabble.com","subject":"Re: Getting started contributing.","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-02-04T13:19:13Z","receivedAt":"2013-02-04T13:19:13Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"adamfraser writes:\n\n> Hi, \n> I would like to start contributing to git and am looking for a small project\n> idea to get started with. On the Small Project Ideas wiki\n> \n\nJust to make it clear: this page is not \"the official TODO-list for\nGit\", but a list where we (essentially me) can throw ideas of things to\nbe implemented.\n\nAs you did, the first thing to do is to discuss ideas on the list, to\nmake sure they are actually wanted.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"208610","messageId":"vpq4nhsmc7p.fsf@grenoble-inp.fr","threadId":"32815","inReplyTo":"7vhaltalre.fsf@alter.siamese.dyndns.org","subject":"Re: Getting started contributing.","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-02-04T13:37:46Z","receivedAt":"2013-02-04T13:37:46Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Junio C Hamano writes:\n\n> adamfraser writes:\n>\n>> I would like to start contributing to git and am looking for a small project\n>> idea to get started with. On the Small Project Ideas wiki\n>> site there is a\n>> suggestion for adding a 'git rebase --status' command that sounds like it\n>> would be good for someone who has little knowledge of the code base.\n>\n> I think the two patches Duy just posted tonight overlap with that\n> topic, and I suspect it would give the end users a better experience\n> to put the information in \"git status\" output rather than a separate\n> \"git rebase\" subcommand.\n\n(I'm the one who wrote the idea on the wiki)\n\n\"git status\" already shows a lot of valuable information about rebase,\nbut my idea was that there's still room for a much more verbose command\n(hence too verbose to appear in the output of \"git branch\" or \"git\nstatus\"), saying eg.\n\n* Which patch is being applied (we can imagine giving just the subject\n line by default, but showing the complete patch with an additional\n --patch option). I often miss that when trying to understand the\n origin of a conflict. I can manually look at file\n .git/rebase-merge/patch (I seem to remember a patch that shows the\n path to this file when rebase stops, but I can't find it anymore), but\n a nice porcelain would be nice.\n\n* What's still on the todo-list\n\nAlso, perhaps this could gather the advices \"(run git rebase \nto )\" currently in the output of \"git status\", and \"git\nstatus may just say \"(run git rebase --status for more information)\"\ninstead of 2 or 3 lines of advices.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"}]}