From: "Santi Béjar" <sbejar@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: git rev-list --boundary from..to
Date: Mon, 23 Apr 2007 16:38:34 +0200 [thread overview]
Message-ID: <8aa486160704230738t75c90777k3787032fa4e348fb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704231624400.8822@racer.site>
On 4/23/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Mon, 23 Apr 2007, Santi Béjar wrote:
>
> > git rev-list ${order} --boundary ${commitlimit}
> >
> > is what is used in gitk. In v1.5.0.3:
> >
> > $ gitk from..to
> >
> > shows the boundary commits next to the child, but it is no longer the
> > case since v1.5.0.3-290-g86ab490.
> >
> > Now all the boundary commits are at the bottom.
> >
> > While at it, when used with --max-count they are at the bottom too,
> > and I understand why, but is there a way to tell "show me the boundary
> > commits next to the child even if it means it takes more time"?
>
> I'd say "--parents", and infer the relevant information.
Sorry, I think I did not expressed it quite well. The "next to the
child" was about the order git-rev-list outputs the commits, not about
the parent information (moreover gitk uses --parents).
> While I agree
> that it was nicer to scripts earlier, IMHO it was incorrect, too.
Sorry but I do not understand what is incorrect. Are you talking about
the regression or about the --max-count question?
Santi
next prev parent reply other threads:[~2007-04-23 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 13:34 git rev-list --boundary from..to Santi Béjar
2007-04-23 14:25 ` Johannes Schindelin
2007-04-23 14:38 ` Santi Béjar [this message]
2007-04-23 14:53 ` 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=8aa486160704230738t75c90777k3787032fa4e348fb@mail.gmail.com \
--to=sbejar@gmail.com \
--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).