On Fri, Mar 7, 2014 at 12:39 AM, Junio C Hamano <gits...@pobox.com> wrote:
> Michael Haggerty <mhag...@alum.mit.edu> writes:
>> I didn't mean to insult all Windows users in general.  I was only
>> referring to the fact that since the default Windows command line is not
>> a POSIX shell, even an experienced Windows user might have trouble
>> figuring out how to execute a shell loop.  Putting this functionality in
>> a git command or script, by contrast, would make it work universally, no
>> fuss, no muss.
> ;-)
> Be it graft or replace, I do not think we want to invite people to
> use these mechansims too lightly to locally rewrite their history
> willy-nilly without fixing their mistakes at the object layer with
> "commit --amend", "rebase", "bfg", etc. in the longer term.  So in
> that sense, adding a command to make it easy is not something I am
> enthusiastic about.
> On the other hand, if the user does need to use graft or replace
> (perhaps to prepare for casting the fixed history in stone with
> filter-branch), it would be good to help them avoid making mistakes
> while doing so and tool support may be a way to do so.
> So, ... I am of two minds.

Maybe if we add a new command (or maybe a script) with a name long and
cryptic-looking enough like "git create-replacement-object" it will
scare casual users from touching it, while power users will be happy
to benefit from it.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to