public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha•warpmail.net>
To: "Shawn O. Pearce" <spearce@spearce•org>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git/spearce.git (Sep 2008, #04; Mon, 22)
Date: Tue, 30 Sep 2008 09:52:34 +0200	[thread overview]
Message-ID: <48E1DAC2.7070304@drmicha.warpmail.net> (raw)
In-Reply-To: <20080929184709.GB21310@spearce.org>

Shawn O. Pearce venit, vidit, dixit 29.09.2008 20:47:
> Here are the topics that have been cooking.  Commits prefixed
> with '-' are only in 'pu' while commits prefixed with '+' are
> in 'next'.

...

> * mg/maint-remote-fix (Mon Sep 22 10:57:51 2008 +0200) 1 commit
>  + make "git remote" report multiple URLs
> 
> (Tip at 7d20e21)
> 
> * bc/maint-diff-hunk-header-fix (Sat Sep 20 15:30:12 2008 -0700) 5 commits
>  + diff hunk pattern: fix misconverted "\{" tex macro introducers
>  + diff: use extended regexp to find hunk headers
>  + diff.*.xfuncname which uses "extended" regex's for hunk header
>    selection
>  + diff.c: associate a flag with each pattern and use it for
>    compiling regex
>  + diff.c: return pattern entry pointer rather than just the hunk
>    header pattern
> 
> (Tip at 96d1a8e)
> 
> The above two are ready for 'maint'.

They are already in maint, as per "What's in..." and the repo.

Cheers,
Michael

  reply	other threads:[~2008-09-30  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 18:47 What's cooking in git/spearce.git (Sep 2008, #04; Mon, 22) Shawn O. Pearce
2008-09-30  7:52 ` Michael J Gruber [this message]
2008-09-30 18:36   ` Shawn O. Pearce
2008-09-30 11:00 ` Alex Riesen
2008-09-30 12:45   ` Alex Riesen
2008-09-30 18:28     ` Shawn O. Pearce

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=48E1DAC2.7070304@drmicha.warpmail.net \
    --to=git@drmicha$(echo .)warpmail.net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=spearce@spearce$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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