c comment would be useful,
something like:
"20171210, 07:08, nn.nn.n:8"
The nn.nn.n:8 meaning the 8th automatic commit (on a compile) after named
branch nn.nn.n)"
Or something similar for any named commit (not necessarily a branch.
I know that some or all of that information is fairly
Hi Russ P,
On Sunday, December 10, 2017 at 5:32:32 AM UTC+1, Russ P wrote:
>
> Thanks for the help, guys. I will have to think about it a bit. I must
> admit that I am concerned about "effing things up" if I try to use new git
> commands for this problem.
>
I understand. Being so powerful, Git
rim save and later regret it (for any of a number of reasons).)
>
>
>
> As far as a comment, without having used git extensively or recently
> (maybe 3-4 years ago), I think some sort of automatic comment would be
> useful, something like:
>
>
>
> "20171210, 0
Hi Russ,
The two matras I see are:
"Branches are cheap, very cheap"
"Git gives (distibutes) control to You"
This means you can branch and commit early and commit often (locally), even
when it might 'break the build' if pushed upstream. (make sure you have this
capability - some shops can't g
Ross,
One extra thing. Have a look at the git.git Sumbitting patches guidelines
(https://github.com/git/git/blob/master/Documentation/SubmittingPatches#L44
#L102, etc.) about writing commit messages, and reveiw the suggested patch
messages in the git mailing list (https://public-inbox.org/git/
Igor,
Thanks for the response!
Yes, I agree--initiating a commit (as you described) manually is pretty easy,
and an automatic trigger may be overkill.
regards,
Randy Kramer
On Sunday, December 10, 2017 08:07:59 AM Igor Djordjevic wrote:
> Even in situation without a build system (so no "post
