Why not rebase instead of merge?
davidterei at gmail.com
Mon Feb 25 01:50:19 CET 2013
doing this allows me when working to make commits more arbitrarily,
such that it suits my development flow. (e.g., a commit simply because
I'm changing from workstation to laptop). Fixing up after the work is
done can result in much nicer, more atomic commits. i.e., hindsight
and all that.
On 24 February 2013 14:50, Stephen Paul Weber <singpolyma at singpolyma.net> wrote:
> Somebody claiming to be Alexander Kjeldaas wrote:
>> Here you might want to do a
>> git rebase -i <when-you-split-from-main-branch>
>> and squash unnecessary commits into larger ones.
> I've never understood why people do this. It seems to violate the purpose
> of making good atomic commits in the first place.
> Stephen Paul Weber, @singpolyma
> See <http://singpolyma.net> for how I prefer to be contacted
> edition right joseph
> ghc-devs mailing list
> ghc-devs at haskell.org
More information about the ghc-devs