git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Lose perl dependency. (fwd)
Date: Fri, 19 Jan 2007 11:56:47 -0800	[thread overview]
Message-ID: <7vps9ag58g.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0701181441010.22628@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Thu, 18 Jan 2007 14:57:15 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Hi,
>
> On Thu, 18 Jan 2007, Simon 'corecode' Schubert wrote:
>
>> Johannes Schindelin wrote:
>> > On Thu, 18 Jan 2007, Simon 'corecode' Schubert wrote:
>> > 
>> > >  for cmt in `git-rev-list --no-merges "$upstream"..ORIG_HEAD \
>> > > -			| @@PERL@@ -e 'print reverse <>'`
>> > > +			| sed -ne '1!G;$p;h'`
>> > 
>> > Why not teach the revision machinery to output in reverse with "--reverse"?
>> 
>> I'm more in favour of "small is beautiful".  Also from looking at the code,
>> this seems to be a bit complicated.
>
> I'm more in favour of "less shell dependecy is beautiful". And from what I 
> can tell, it should be relatively easy:
>
> ---
>
> 	14 insertions and 11 deletions stem from moving (and extern'ing) 
> 	reverse_commit_list() from merge-recursive.c to commit.c
>
> 	So the change is actually 9 insertions and one deletion.

I think this is sane but I hate to having to worry about
possible fallouts from giving --reverse in setup_revisions() to
make it available to everybody.  E.g. things like "what happens
when you say "git format-patch --reverse HEAD~3".

Nevertheless, moving reverse_commit_list out of merge-recursive
is a good clean-up.

  parent reply	other threads:[~2007-01-19 19:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 10:49 [PATCH] Lose perl dependency. (fwd) Johannes Schindelin
2007-01-18 11:52 ` Simon 'corecode' Schubert
2007-01-18 13:57   ` Johannes Schindelin
2007-01-18 14:03     ` Simon 'corecode' Schubert
2007-01-18 15:00     ` Andy Parkins
2007-01-18 15:08       ` Johannes Schindelin
2007-01-19 19:56     ` Junio C Hamano [this message]
2007-01-19 23:54       ` Johannes Schindelin
2007-01-20  0:35         ` Junio C Hamano
2007-01-20  1:18           ` Johannes Schindelin
2007-01-20  1:21             ` Junio C Hamano
2007-01-20  1:31               ` Johannes Schindelin
2007-01-20  3:30             ` Junio C Hamano
2007-01-20  4:02               ` Simon 'corecode' Schubert
2007-01-20  9:28               ` Johannes Schindelin
2007-01-20 18:31                 ` Junio C Hamano
2007-01-20 22:04                   ` Johannes Schindelin
2007-01-21  0:37                     ` Robin Rosenberg
2007-01-21  1:39                       ` Johannes Schindelin
2007-01-21  2:32                         ` Bill Lear
2007-01-21  3:17                           ` Junio C Hamano
2007-01-21 22:16                             ` David Kågedal
2007-01-21 22:35                               ` Johannes Schindelin
2007-01-23 13:18                               ` Krzysztof Halasa
2007-01-23 13:50                                 ` David Kågedal
2007-01-23 14:34                                   ` Krzysztof Halasa
2007-01-23 17:07                                     ` Randal L. Schwartz
2007-01-23 23:27                                       ` Krzysztof Halasa
2007-01-23 23:48                                         ` Krzysztof Halasa
2007-01-21  2:56                     ` Simon 'corecode' Schubert
2007-01-21 11:19                       ` [PATCH] Teach revision machinery about --reverse Johannes Schindelin

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=7vps9ag58g.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).