git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Adam <dreamingforward-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: git add "This file is for the blah class"
Date: Sun, 19 Aug 2012 18:03:43 -0500	[thread overview]
Message-ID: <CAMjeLr9eENN6h0woKcszeP0xWN8-Rt6vG8zivPO6Zct4wgBFaA@mail.gmail.com> (raw)
In-Reply-To: <02ad01cd7e5c$e95b7af0$bc1270d0$@com>

[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]

On Sun, Aug 19, 2012 at 5:49 PM, NightShade <nightshade1632-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>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.


[-- Attachment #2: Type: text/html, Size: 3154 bytes --]

      parent reply	other threads:[~2012-08-19 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-19 18:45 git add "This file is for the blah class" theProphet
     [not found] ` <004a01cd7e59$58332b70$08998250$@com>
     [not found]   ` <CAMjeLr_chpUsb8L2bySZ9ccAGa2NtkcxnBTJT2zN0WcevF2mnQ@mail.gmail.com>
     [not found]     ` <02ad01cd7e5c$e95b7af0$bc1270d0$@com>
2012-08-19 23:03       ` Mark Adam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMjeLr9eENN6h0woKcszeP0xWN8-Rt6vG8zivPO6Zct4wgBFaA@mail.gmail.com \
    --to=dreamingforward-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).