[kwlug-disc] Advanced(?) Git usage question

Chris Frey cdfrey at foursquare.net
Tue Apr 15 18:09:19 EDT 2014


On Thu, Apr 10, 2014 at 08:37:13AM -0400, John Johnson wrote:
> IMO The quoted comment above makes the case for:
> a) frequent commits - often isolated to a given issue and

Definitely.


> b) explicit and consistent commit messages

Yep.


And I wouldn't be afraid of detail too.  Some commit messages can
contain whole emails for background data, etc.


> This might suggest the use of an additional tool, a bug tracking
> tool, Bugzilla perhaps.

Well, if you're consistent in including bugzilla ID's in your commit
messages, perhaps, but I guess it also depends on the size of your project.
I haven't had the need for bugzilla yet.


> FWIW I have been using a text file as a log file and have, when I
> remember, logging git activity to this log file, for example (using
> bash):
> $ git status >> mygitlog.txt
> $ git commit -am "this is a message to be associated with the commit" >> mygitlog.txt

There is the git reflog too, btw.  This keeps a log of what you've been
doing, and even if you "delete" a commit, you can still find traces of it,
and therefore recover it, using the reflog.  (As long as you don't git-gc
it away first, of course.)

- Chris





More information about the kwlug-disc mailing list