From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Removal of "--merge-order"?
Date: Fri, 24 Feb 2006 11:25:24 -0800 [thread overview]
Message-ID: <7v8xs0a7a3.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0602240824110.3771@g5.osdl.org> (Linus Torvalds's message of "Fri, 24 Feb 2006 08:32:43 -0800 (PST)")
Linus Torvalds <torvalds@osdl.org> writes:
> In other words, I'd really prefer if it was gone. Some of the things I
> might do to git-rev-list would be much simpler if I didn't have to worry
> about merge-order, and the way it interfaces with the rest of
> git-rev-list.
>
> Comments?
>
> Linus
I am really glad you brought it up. I would not miss it at all.
prev parent reply other threads:[~2006-02-24 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 16:32 Removal of "--merge-order"? Linus Torvalds
2006-02-24 16:53 ` Randy.Dunlap
2006-02-24 17:23 ` Linus Torvalds
2006-02-24 17:32 ` Ryan Anderson
2006-02-24 17:47 ` Randy.Dunlap
2006-02-24 18:07 ` Linus Torvalds
2006-02-24 18:10 ` Randy.Dunlap
2006-02-24 21:37 ` Johannes Schindelin
2006-02-24 19:25 ` Junio C Hamano [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=7v8xs0a7a3.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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