From: Stefan Beller <stefanbeller@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [RFC] improving advice message from "git commit" during a merge
Date: Thu, 28 Aug 2014 14:17:50 +0200 [thread overview]
Message-ID: <53FF1DEE.8030504@gmail.com> (raw)
In-Reply-To: <xmqq4mwxeqr7.fsf@gitster.dls.corp.google.com>
On 27.08.2014 20:23, Junio C Hamano wrote:
> I am not doing this myself soon, though. Hint, hint...
I asked once upon a time, if there was a place,
which collects such topics for casual contributors and new comers.
Would you mind to update the leftover bits at
http://git-blame.blogspot.de/search?q=leftover&by-date=true
?
Thanks,
Stefan
next prev parent reply other threads:[~2014-08-28 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 18:23 [RFC] improving advice message from "git commit" during a merge Junio C Hamano
2014-08-27 19:18 ` Jeff King
2014-08-27 19:28 ` Junio C Hamano
2014-08-28 9:46 ` [PATCH] merge, pull: stop advising 'commit -a' in case of conflict Matthieu Moy
2014-08-28 17:28 ` Junio C Hamano
2014-08-28 17:41 ` Matthieu Moy
2014-08-28 18:16 ` Jonathan Nieder
2014-08-28 18:36 ` Junio C Hamano
2014-08-29 6:44 ` Matthieu Moy
2014-08-28 12:17 ` Stefan Beller [this message]
2014-08-28 17:11 ` [RFC] improving advice message from "git commit" during a merge Junio C Hamano
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=53FF1DEE.8030504@gmail.com \
--to=stefanbeller@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).