From: Fredrik Tolf <fredrik@dolda2000•com>
To: git@vger•kernel.org
Subject: Volume of commits
Date: Thu, 12 Jul 2007 15:16:47 +0200 [thread overview]
Message-ID: <m3ps2xu5hc.fsf@pc7.dolda2000.com> (raw)
Hi List,
I was wondering -- whenever I see Git patches committed to projects
like the Linux kernel or Git itself, the commits always seems to be
committing rather large changes and be rather well-defined in terms of
what they change.
When I develop for myself, I usually commit incrementally quite a
bit, if for no other reason because Git won't let me switch between
branches if I don't commit first. I usually try to keep my commits
well-defined, but I don't manage to get anywhere close to what I see
when I look at the history of Linux or Git.
So what I'm wondering is how you people manage to do this? Do you
actually always commit changes this way (and, in that case, how do you
switch between branches)? Or do you somehow aggregate the smaller
commits into larger patches and recommit them? Or is there some third
possibility that I'm missing?
Fredrik Tolf
next reply other threads:[~2007-07-12 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 13:16 Fredrik Tolf [this message]
2007-07-12 13:29 ` Volume of commits VMiklos
2007-07-12 13:59 ` Johannes Schindelin
2007-07-13 10:30 ` Sven Verdoolaege
2007-07-13 12:46 ` Alex Riesen
2007-07-21 17:09 ` [PATCH] rebase -i: call editor just once for a multi-squash Johannes Schindelin
2007-07-21 17:12 ` Volume of commits Johannes Schindelin
2007-07-12 13:49 ` Karl Hasselström
2007-07-12 14:03 ` Karl Hasselström
2007-07-12 14:51 ` Fredrik Tolf
2007-07-12 16:09 ` Joshua N Pritikin
2007-07-12 16:21 ` Karl Hasselström
2007-07-12 16:46 ` Linus Torvalds
2007-07-13 0:40 ` Jakub Narebski
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=m3ps2xu5hc.fsf@pc7.dolda2000.com \
--to=fredrik@dolda2000$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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