public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce•org>
To: "Jeffrey C. Ollie" <jeff@ocjtech•us>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Documentation: fix git-config.xml generation
Date: Thu, 24 May 2007 00:47:36 -0400	[thread overview]
Message-ID: <20070524044736.GH28023@spearce.org> (raw)
In-Reply-To: <1179981812.3682.16.camel@lt21223.campus.dmacc.edu>

"Jeffrey C. Ollie" <jeff@ocjtech•us> wrote:
> On Wed, 2007-05-23 at 21:22 -0700, Junio C Hamano wrote:
> > "Jeffrey C. Ollie" <jeff@ocjtech•us> writes:
> > 
> > > On Wed, 2007-05-23 at 18:16 -0400, James Bowes wrote:
> > >>
> > >> With asciidoc 8.1.0 and xmlto 0.0.18, git-config.xml failed to
> > >> validate. This patch just makes the asciidoc formatting for
> > >> branch.autosetupmerge the same as the other config options.
> > >
> > > I can confirm that this patch fixes the validation errors...
> > 
> > Yup, already pushed out about 7 hours ago.
> 
> I do not see it in any of the public git repos.  Is there some
> synchronization interval I need to wait for?

kernel.org has mirroring lags.  When Junio pushes to kernel.org
he also pushes to repo.or.cz/alt-git.git.  That's usually where
I fetch from, as there's no mirroring lag at all.

Note that repo.or.cz also has a git.git, which is a mirror of
kernel.org's mirrors, so its uh, way way behind sometimes.  ;-)

-- 
Shawn.

  reply	other threads:[~2007-05-24  4:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 22:16 [PATCH] Documentation: fix git-config.xml generation James Bowes
2007-05-24  4:10 ` Jeffrey C. Ollie
2007-05-24  4:22   ` Junio C Hamano
2007-05-24  4:43     ` Jeffrey C. Ollie
2007-05-24  4:47       ` Shawn O. Pearce [this message]
2007-05-24  4:55         ` Jeffrey C. Ollie

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=20070524044736.GH28023@spearce.org \
    --to=spearce@spearce$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jeff@ocjtech$(echo .)us \
    /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