From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git UI nit
Date: Wed, 06 Dec 2006 16:41:31 +0100 [thread overview]
Message-ID: <4576E4AB.8010608@xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.63.0612061619120.28348@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin escreveu:
> Actually, I like it that short.
>
> We had an email on this list, where the poster said he could not merge
> with Git. It turned out that the merge failed with conflicts, but he
> did not bother reading through the messages, apparently because they were
> too many.
good point.
--
prev parent reply other threads:[~2006-12-06 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 14:22 git UI nit Han-Wen Nienhuys
2006-12-06 14:46 ` Johannes Schindelin
2006-12-06 15:09 ` Han-Wen Nienhuys
2006-12-06 15:20 ` Johannes Schindelin
2006-12-06 15:36 ` Jakub Narebski
2006-12-06 16:04 ` Han-Wen Nienhuys
2006-12-06 16:23 ` Jakub Narebski
2006-12-06 15:41 ` Han-Wen Nienhuys [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=4576E4AB.8010608@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=Johannes.Schindelin@gmx.de \
--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).