From: theProphet <dreamingforward-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: git add "This file is for the blah class"
Date: Sun, 19 Aug 2012 11:45:46 -0700 (PDT) [thread overview]
Message-ID: <e0c6edc0-9ff5-491e-9e74-d91cd1330f47@googlegroups.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1202 bytes --]
next reply other threads:[~2012-08-19 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 18:45 theProphet [this message]
[not found] ` <004a01cd7e59$58332b70$08998250$@com>
[not found] ` <CAMjeLr_chpUsb8L2bySZ9ccAGa2NtkcxnBTJT2zN0WcevF2mnQ@mail.gmail.com>
[not found] ` <02ad01cd7e5c$e95b7af0$bc1270d0$@com>
2012-08-19 23:03 ` git add "This file is for the blah class" Mark Adam
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=e0c6edc0-9ff5-491e-9e74-d91cd1330f47@googlegroups.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).