{"thread":{"id":"31284","subject":"git add \"This file is for the blah class\"","startedAt":"2012-08-19T18:45:46Z","lastAt":"2012-08-19T23:03:43Z","messageCount":2,"participants":["theProphet","Mark Adam"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"197293","messageId":"e0c6edc0-9ff5-491e-9e74-d91cd1330f47@googlegroups.com","threadId":"31284","inReplyTo":null,"subject":"git add \"This file is for the blah class\"","fromName":"theProphet","fromEmail":"dreamingforward-re5jqeeqqe8avxtiumwx3w@public.gmane.org","sentAt":"2012-08-19T18:45:46Z","receivedAt":"2012-08-19T18:45:46Z","isPatch":false,"sender":{"key":"dreamingforward-re5jqeeqqe8avxtiumwx3w@public.gmane.org","avatar":null},"body":"I'm finding it annoying when browsing repositories at github and such that \nthe description on every file and directory is only the last commit message \ngiven for that file.\n\nI think it would be much more organizationally useful if the \"git add\" \ncommand accepted a message that will be associated with that file that \ndescribes its purpose.  A file name just isn't adequate to do the job and \nthere's nowhere else where this is tracked.\n\nThanks guys!\n\nmark\ngithub/Social-Garden.\n\n\n-- \nYou received this message because you are subscribed to the Google Groups \"Git for human beings\" group.\nTo view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/z8QL0uzNBCIJ.\nTo post to this group, send email to git-users-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org\nTo unsubscribe from this group, send email to git-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org\nFor more options, visit this group at http://groups.google.com/group/git-users?hl=en.\n\n"},{"id":"197307","messageId":"CAMjeLr9eENN6h0woKcszeP0xWN8-Rt6vG8zivPO6Zct4wgBFaA@mail.gmail.com","threadId":"31284","inReplyTo":"02ad01cd7e5c$e95b7af0$bc1270d0$@com","subject":"Re: git add \"This file is for the blah class\"","fromName":"Mark Adam","fromEmail":"dreamingforward-re5jqeeqqe8avxtiumwx3w@public.gmane.org","sentAt":"2012-08-19T23:03:43Z","receivedAt":"2012-08-19T23:03:43Z","isPatch":false,"sender":{"key":"dreamingforward-re5jqeeqqe8avxtiumwx3w@public.gmane.org","avatar":null},"body":"On Sun, Aug 19, 2012 at 5:49 PM, NightShade <nightshade1632-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>wrote:\n\n> Maybe something like\n>\n> Create initial version of class file or files “maybe even empty files”\n> then use git add and git commit to store them in the repo and finally git\n> notes to add the description.****\n>\n> ** **\n>\n> Since I mainly use git with drupal and just need to record when I create a\n> site specific folder or add / update a module I have a very basic working\n> knowledge of git. Based on how I interpret the below excerpt from the\n> git-notes man page I think the above would work as long as there is not a\n> commit between the initial addition/commit of the class files and the note.\n> ****\n>\n> ** **\n>\n> This is from the git-notes man page at kernel.org****\n>\n> A typical use of notes is to supplement a commit message without changing\n> the commit itself. Notes can be shown by *git log* along with the\n> original commit message.****\n>\n> ** **\n>\n>\n> Yes, that's all decent, but I'm trying to create a habitual methodology\nabout the documentation of files so that it helps the community as standard\npractice.  The perfect place is really on the git add command line.  I\nwould suggest it at the main dev list, but I recently signed on and have\nestablished any status there....  So will wait...\n\nmark\n\n-- \nYou received this message because you are subscribed to the Google Groups \"Git for human beings\" group.\nTo post to this group, send email to git-users-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org\nTo unsubscribe from this group, send email to git-users+unsubscribe@googlegroups.com.\nFor more options, visit this group at http://groups.google.com/group/git-users?hl=en.\n\n"}]}