git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: David Greene <greened@obbligato.org>
To: git@vger.kernel.org
Cc: techlivezheng@gmail.com, alex.crezoff@gmail.com,
	davvid@gmail.com, cbailey32@bloomberg.net, danny0838@gmail.com,
	prohaska@zib.de, th.acker@arcor.de, sschuberth@gmail.com,
	peff@peff.net, gitter.spiros@gmail.com, nod.helm@gmail.com,
	gitster@pobox.com
Subject: Remote subtree split --annotate
Date: Sat,  2 Jan 2016 14:36:23 -0600	[thread overview]
Message-ID: <1451766984-4648-1-git-send-email-greened@obbligato.org> (raw)

This is a fairly simple patch to remove subtree's split --annotate
option.  The intent of the option is to mark commits split from
a subdirectory but git has other tools more suitable for editing
commit messages.  Given --annotate an --unannotate feature seems
obvious and in fact was requested at one point.  Discussion ensued
and it became clear that the definition of --unannotate is not
obvious given the multitude of ways one might want to rewrite a
commit message.

Since it is simple to run other git commit message rewriting tools
on commits split from a subdirectory, it seems best to just
get git-subtree out of the commit rewriting business altogether.

             reply	other threads:[~2016-01-02 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 20:36 David Greene [this message]
2016-01-02 20:36 ` [PATCH] contrib/subtree: Remove --annotate David Greene
2016-01-03  9:06   ` Sebastian Schuberth
2016-01-04 15:53     ` greened

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=1451766984-4648-1-git-send-email-greened@obbligato.org \
    --to=greened@obbligato.org \
    --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=nod.helm@gmail.com \
    --cc=peff@peff.net \
    --cc=prohaska@zib.de \
    --cc=sschuberth@gmail.com \
    --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).