Re: Considering teaching plumbing to users harmful
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- Jul 16, 2008, 19:22 UTC
- Message-ID
- <32541b130807161222y68f447c9n5afa6f14d871fe50@mail.gmail.com>
- In-Reply-To
- <20080716185930.GP32184@machine.or.cz>
On 7/16/08, Petr Baudis <pasky@suse.cz> wrote:
Show 14 quoted lines
> On Wed, Jul 16, 2008 at 02:51:30PM -0400, Avery Pennarun wrote: > > On 7/16/08, Junio C Hamano <gitster@pobox.com> wrote: > > > You can skip merges with "git log --no-merges", just in case you didn't > > > know. > > Perhaps this is mostly a user education or documentation issue. I > > know about --no-merges, but it's unclear that this is really a safe > > thing to use, particularly if some of your merges have conflicts. > > Leaving them out leaves out an important part of history. Do you use > > this option yourself? > > Whereas if you rebase, not only you don't show the conflicts resolution, > you didn't even _store_ it in the first place. That isn't much of an > improvement. :-) (This is the main reason why I prefer to avoid rebase > unless absolutely necessary for the workflow.)
The key here is that I'd expect "git log -p" with a rebased merge at least shows me the actual changes that are in my repository. "git log --no-merges" will actually omit things.
Avery