(H.24/08/20 8:03), Mark Adam wrote:
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 don't think it is. "git add" isn't there t
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
ooglegroups.com
Subject: Re: [git-users] git add "This file is for the blah class"
On Sun, Aug 19, 2012 at 5:24 PM, NightShade
wrote:
Mark,
Have you looked into the notes subcommand for git? I have not personally
used it myself so I'm not certain if it will work for what you
On Sun, Aug 19, 2012 at 5:24 PM, NightShade wrote:
> Mark,
>
> ** **
>
> Have you looked into the notes subcommand for git? I have not personally
> used it myself so I’m not certain if it will work for what you want or not
> but it does sound like it would at least be a start for the type of
>
users@googlegroups.com [mailto:git-users@googlegroups.com] On
Behalf Of theProphet
Sent: Sunday, August 19, 2012 12:46 PM
To: git-users@googlegroups.com
Cc: g...@vger.kernel.org
Subject: [git-users] git add "This file is for the blah class"
I'm finding it annoying when browsing repositories at
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 w
