# git add "This file is for the blah class" 2 messages from 2012-08-19 to 2012-08-19. Participants: theProphet, Mark Adam. Thread: https://gitlist.dev/t/31284 ## theProphet, 2012-08-19 18:45 Subject: git add "This file is for the blah class" Message-ID: URL: https://gitlist.dev/e/e0c6edc0-9ff5-491e-9e74-d91cd1330f47%40googlegroups.com ``` I'm finding it annoying when browsing repositories at github and such that the description on every file and directory is only the last commit message given for that file. I think it would be much more organizationally useful if the "git add" command accepted a message that will be associated with that file that describes its purpose. A file name just isn't adequate to do the job and there's nowhere else where this is tracked. Thanks guys! mark github/Social-Garden. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/z8QL0uzNBCIJ. To post to this group, send email to git-users-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to git-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/git-users?hl=en. ``` ## Mark Adam, 2012-08-19 23:03 Subject: Re: git add "This file is for the blah class" Message-ID: URL: https://gitlist.dev/e/CAMjeLr9eENN6h0woKcszeP0xWN8-Rt6vG8zivPO6Zct4wgBFaA%40mail.gmail.com In-Reply-To: <02ad01cd7e5c$e95b7af0$bc1270d0$@com> ``` On Sun, Aug 19, 2012 at 5:49 PM, NightShade wrote: > Maybe something like > > Create initial version of class file or files “maybe even empty files” > then use git add and git commit to store them in the repo and finally git > notes to add the description.**** > > ** ** > > Since I mainly use git with drupal and just need to record when I create a > site specific folder or add / update a module I have a very basic working > knowledge of git. Based on how I interpret the below excerpt from the > git-notes man page I think the above would work as long as there is not a > commit between the initial addition/commit of the class files and the note. > **** > > ** ** > > This is from the git-notes man page at kernel.org**** > > A typical use of notes is to supplement a commit message without changing > the commit itself. Notes can be shown by *git log* along with the > original commit message.**** > > ** ** > > > Yes, that's all decent, but I'm trying to create a habitual methodology about the documentation of files so that it helps the community as standard practice. The perfect place is really on the git add command line. I would suggest it at the main dev list, but I recently signed on and have established any status there.... So will wait... mark -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to git-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en. ```