06.07.2011 11:21, Erich Titl пишет:
> Most of the above is completely meaningless to the reader, as the commit
> messages just address the full repository.
You can see commits that affects some file (git log --follow
), and if messages are too generic - '-u' option will
help you to see what was r
06.07.2011 11:15, Erich Titl пишет:
> Hi Andrew
>
> at 06.07.2011 09:43, Andrew wrote:
>> 06.07.2011 09:34, Erich Titl пишет:
>>> Hi folks
>>>
>>> Trying to clean up and pull together all the various source and config
>>> files I am wondering where the fine version info and modification
>>> history
Andrew
just to show you what I mean
>
commit 1f8bb69aa9b81db2132e3822a21bd6bd879b5cf2
Author: mega
Date: Tue Jun 14 23:49:55 2011 +0200
fixed parsing bug for free memory, probably due to different formatting
of the busybox free applet
commit 9
Hi Andrew
at 06.07.2011 09:43, Andrew wrote:
> 06.07.2011 09:34, Erich Titl пишет:
>> Hi folks
>>
>> Trying to clean up and pull together all the various source and config
>> files I am wondering where the fine version info and modification
>> history within the source files went. Call me old fash
06.07.2011 09:34, Erich Titl пишет:
> Hi folks
>
> Trying to clean up and pull together all the various source and config
> files I am wondering where the fine version info and modification
> history within the source files went. Call me old fashioned, but I
> personally like it. Is that something
Hi folks
Trying to clean up and pull together all the various source and config
files I am wondering where the fine version info and modification
history within the source files went. Call me old fashioned, but I
personally like it. Is that something that just went overboard in the
GIT frenzy?
ch
