[git-users] Question about commit size

2012-06-20 Thread paymaster
Dear all..

How can I know commit size?

Is there any solution?

Thanks.

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] Question about commit size

2012-06-20 Thread Serge Matveenko
On Wed, Jun 20, 2012 at 11:43 AM, paymaster baekseon...@gmail.com wrote:
 How can I know commit size?

What is size? A number of lines affected? Raw patch size in bytes?
Compressed patch size in bytes? Mount of data transferred via push
maybe?


-- 
Serge Matveenko
se...@matveenko.ru
http://www.ohloh.net/accounts/lig
http://ru.linkedin.com/in/sergematveenko

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: Question about commit size

2012-06-20 Thread paymaster
Thanks for your reply :-)

I mean the mount of data transferred via push.

thanks

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: Question about commit size

2012-06-20 Thread Thomas Ferris Nicolaisen
git push displays this by default:

➜  ~/projects/agnes/[master]git push
Counting objects: 17, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (15/15), done.
Writing objects: 100% (15/15), 1.35 KiB, done.

The above push resulted in a transfer of 1.35 KiB, which is the same as, or 
more correct term for what we call 
Kilobyteshttp://en.wikipedia.org/wiki/Kibibyte, 
or KB.

On Wednesday, June 20, 2012 10:08:39 AM UTC+2, paymaster wrote:

 Thanks for your reply :-) 

 I mean the mount of data transferred via push. 

 thanks 


-- 
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/-/lML6tnSkMeAJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] Re: git pull asks for commit comment

2012-06-20 Thread Konstantin Khomoutov
On Tue, 19 Jun 2012 12:02:26 -0700 (PDT)
Dan Hirsmuller-Counts xpemda...@gmail.com wrote:

  This is one of the recent changes in Git to make it more user
  friendly. More specifically in this point, help users avoid these
  automatic merge messages that can sometime be a bit ugly.
 
  From http://git-scm.com/docs/git-pull :
  --no-edit
 
  Invoke an editor before committing successful mechanical merge to
  further edit the auto-generated merge message, so that the user can
  explain and justify the merge. The --no-editoption can be used to
  accept the auto-generated message (this is generally discouraged).
  The --edit option is still useful if you are giving a draft message
  with the -m option from the command line and want to edit it in the
  editor.
 
 How is it more user friendly to make the user submit a message every
 time they do a PULL? To me the merge caused by a pull is just assumed
 and I cannot think of a situation where I would modify the default
 merge message. 

Because you're not doing pull, you're merging someone else's changes
into your changes, and this produces a state of the codebase which has
to be tested.  To put it differently, you're usually not just pull,
you make a conscious decision to reconcile two (or more) diverging lines
of development, and this is *not* a no-brainer automated thing.
If you do not beleive this, read this post [1] (the Disaster 2:
Merging Without Understanding part, specifically) which has been
recently referred to in [2].

P.S.
Please don't top-post.

1. http://www.randyfay.com/node/89
2. http://stackoverflow.com/q/11058312/720999

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.