Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: git update delay  [Re: FYI, small patch required to resync git from  cvs]
Date: Sun, 25 Oct 2009 15:49:00 -0000	[thread overview]
Message-ID: <878wez8oob.fsf@meyering.net> (raw)
In-Reply-To: <20091025152620.GA18409@host0.dyn.jankratochvil.net> (Jan 	Kratochvil's message of "Sun, 25 Oct 2009 16:26:21 +0100")

Jan Kratochvil wrote:
> On Sun, 25 Oct 2009 16:02:02 +0100, Jim Meyering wrote:
>> It should propagate to the public git repo within the hour.
>
> This delay complicates it a bit sometimes for preperation of dependent
> patches.  i am not aware of the required + available performance resources but
> it could the update run more often?  (if not 1 then for example 5 minutes)

Yes, I know how aggravating that can be.
Luckily, the repositories for which I suffered the most have all
converted to git upstream, now ;-)

Currently the gdb cvs-to-git sync process runs once per hour, but a run
can take over 20 minutes when every ,v file has been touched by a tag,
so I can't increase the frequency by much.  Even at the best of times
(I've just confirmed) it takes at least 7 minutes.

I've just doubled its frequency, so now it runs at 8 and 38 minutes
after each hour.


  reply	other threads:[~2009-10-25 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 15:26 FYI, small patch required to resync git from cvs Jim Meyering
2009-10-25 15:43 ` git update delay [Re: FYI, small patch required to resync git from cvs] Jan Kratochvil
2009-10-25 15:49   ` Jim Meyering [this message]
2009-10-25 16:02     ` Jan Kratochvil
2009-10-25 16:08       ` Jim Meyering

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=878wez8oob.fsf@meyering.net \
    --to=jim@meyering.net \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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