From: Sebastian Schuberth <sschuberth@gmail.com>
To: David Greene <greened@obbligato.org>
Cc: Git Mailing List <git@vger.kernel.org>,
techlivezheng@gmail.com, alex.crezoff@gmail.com,
davvid@gmail.com, cbailey32@bloomberg.net, danny0838@gmail.com,
Steffen Prohaska <prohaska@zib.de>,
th.acker@arcor.de, Jeff King <peff@peff.net>,
gitter.spiros@gmail.com, nod.helm@gmail.com,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] contrib/subtree: Remove --annotate
Date: Sun, 3 Jan 2016 10:06:36 +0100 [thread overview]
Message-ID: <CAHGBnuMtmUx_NwETPv+xU23PG8vmWm6jWpoRXc9+2qXok5Ak4w@mail.gmail.com> (raw)
In-Reply-To: <1451766984-4648-2-git-send-email-greened@obbligato.org>
On Sat, Jan 2, 2016 at 9:36 PM, David Greene <greened@obbligato.org> wrote:
> commit messages. git has other tools more suited to rewriting
> commit messages and it's easy enough to use them after a subtree
> split.
For completeness, it probably would be a good idea to name examples
for such more suitable tools as part of the commit message.
--
Sebastian Schuberth
next prev parent reply other threads:[~2016-01-03 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 20:36 Remote subtree split --annotate David Greene
2016-01-02 20:36 ` [PATCH] contrib/subtree: Remove --annotate David Greene
2016-01-03 9:06 ` Sebastian Schuberth [this message]
2016-01-04 15:53 ` greened
-- strict thread matches above, loose matches on Subject: below --
2016-01-05 3:05 [PATCH v2] Remote subtree split --annotate David Greene
2016-01-05 3:05 ` [PATCH] contrib/subtree: Remove --annotate David Greene
2016-01-05 17:33 ` Junio C Hamano
2016-01-05 21:35 ` David A. Greene
2016-01-15 18:54 ` Junio C Hamano
2016-01-17 23:30 ` David A. Greene
2016-01-18 1:29 ` Junio C Hamano
2016-06-28 11:10 ` David A. Greene
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHGBnuMtmUx_NwETPv+xU23PG8vmWm6jWpoRXc9+2qXok5Ak4w@mail.gmail.com \
--to=sschuberth@gmail.com \
--cc=alex.crezoff@gmail.com \
--cc=cbailey32@bloomberg.net \
--cc=danny0838@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitter.spiros@gmail.com \
--cc=greened@obbligato.org \
--cc=nod.helm@gmail.com \
--cc=peff@peff.net \
--cc=prohaska@zib.de \
--cc=techlivezheng@gmail.com \
--cc=th.acker@arcor.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).