From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Volume of commits
Date: Fri, 13 Jul 2007 02:40:41 +0200 [thread overview]
Message-ID: <f76hm5$fde$1@sea.gmane.org> (raw)
In-Reply-To: m3ps2xu5hc.fsf@pc7.dolda2000.com
Fredrik Tolf wrote:
> 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.
First, if you commit only to switch branches you can always instead
of adding commit on top of whis WIP commit, just --amend it.
Second, there is git-stash just created for saving state to go back
to it.
Third, I guess that the neat patch series are result of reworking
existing series using tools like StGIT (which I use and find very
nice to work with, going and correcting back and forth between patches
in series), or guilt (similar to StGIT), or git-gui, or new interactive mode
of git-rebase, or git-cherry-pick...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-07-13 0:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 13:16 Volume of commits Fredrik Tolf
2007-07-12 13:29 ` 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 [this message]
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='f76hm5$fde$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).