All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git log filtering
Date: Fri, 9 Feb 2007 16:02:24 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.63.0702091557420.22628@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <20070209132239.GA727@coredump.intra.peff.net>

Hi,

On Fri, 9 Feb 2007, Jeff King wrote:

> On Fri, Feb 09, 2007 at 02:13:18PM +0100, Johannes Schindelin wrote:
> 
> > The difference, of course, is that with the "other things", we either have 
> > no alternative (if you do not have curl, you cannot use HTTP transport), 
> > or we have workalikes (if you don't use openssl, the (possibly slower) 
> > SHA1 replacements take effect).
> 
> I'm not a pcre expert, but I thought most of the additions to posix
> extended regular expressions were expressed through constructs that
> would otherwise be invalid patterns.

So, once pcre is used, you can use these constructs. Even in scripts. 
Which just so happen to break on platforms where git is not compiled with 
pcre support.

Or do you suggest checking (in git!) if the pattern is a pcre special or 
not? That would be insane.

> > We _used_ to rely on external "diff" and "merge", but have them as 
> > inbuilt components, exactly to avoid "if you have a slightly differing 
> > setup, git behaves differently".
> 
> But you're OK with "if you didn't built against curl, http transport 
> just doesn't work."

Yes, I am. Since HTTP is itself only a second-class citizen.

> So what if there is a '--pcre' option and a corresponding config option? 
> Thus you get the same results always, unless you use --pcre and it's not 
> built, in which case git dies. That seems to be the moral equivalent of 
> the curl situation.

I might be wrong, but most of git does not depend on HTTP.

> At any rate, you didn't address my original point, which is _all_ of 
> those options have drawbacks. I think the drawbacks of re-writing or 
> re-packaging a regular expression library outweigh those of adding the 
> dependency (or even having slightly irregular behavior).

This is only because you do not really have problems with dependencies. 
You just install, or compile, the dependent thing, which happens to be no 
hassle, since you use Linux. And you can compile & install things.

Once everybody runs Linux, and is allowed to compile & install things, I 
will no longer complain about trillions of dependencies.

Ciao,
Dscho

  reply	other threads:[~2007-02-09 15:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 16:41 git log filtering Don Zickus
2007-02-07 16:55 ` Jakub Narebski
2007-02-07 17:01 ` Uwe Kleine-König
2007-02-07 17:12   ` Johannes Schindelin
2007-02-07 17:12 ` Linus Torvalds
2007-02-07 17:25   ` Johannes Schindelin
     [not found]     ` <7v64ad7l12.fsf@assigned-by-dhcp.cox.net>
2007-02-07 21:03       ` Linus Torvalds
2007-02-07 21:09         ` Junio C Hamano
2007-02-07 21:53           ` Linus Torvalds
2007-02-08  6:16             ` Jeff King
2007-02-08 18:06               ` Johannes Schindelin
2007-02-08 22:33                 ` Jeff King
2007-02-09  0:18                   ` Johannes Schindelin
2007-02-09  0:23                     ` Shawn O. Pearce
2007-02-09  0:45                       ` Johannes Schindelin
2007-02-09 10:15                       ` Sergey Vlasov
2007-02-09  1:59                     ` Jeff King
2007-02-09 13:13                       ` Johannes Schindelin
2007-02-09 13:22                         ` Jeff King
2007-02-09 15:02                           ` Johannes Schindelin [this message]
2007-03-07 17:37               ` pcre performance, was " Johannes Schindelin
2007-03-07 18:03                 ` Paolo Bonzini
2007-02-08  1:59         ` Horst H. von Brand
2007-02-07 18:16   ` Linus Torvalds
2007-02-07 19:49     ` Fix "git log -z" behaviour Linus Torvalds
2007-02-07 19:55       ` Junio C Hamano
2007-02-07 22:53       ` Don Zickus
2007-02-07 23:05         ` Linus Torvalds
2007-02-08 22:34       ` Junio C Hamano
2007-02-10  7:32         ` Junio C Hamano
2007-02-10  9:36           ` Junio C Hamano
2007-02-10 17:09             ` Linus Torvalds
2007-02-07 18:19   ` git log filtering Don Zickus
2007-02-07 18:27     ` Linus Torvalds

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=Pine.LNX.4.63.0702091557420.22628@wbgn013.biozentrum.uni-wuerzburg.de \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.