From: Josh Triplett <josh@freedesktop.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-sparse@vger.kernel.org
Subject: Git mirror delay
Date: Tue, 27 Feb 2007 18:55:42 -0800 [thread overview]
Message-ID: <45E4EF2E.4050101@freedesktop.org> (raw)
In-Reply-To: <1172625480.2363.21.camel@dv>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
Pavel Roskin wrote:
> On Tue, 2007-02-27 at 10:40 -0800, Josh Triplett wrote:
>> Oleg Nesterov wrote:
>>> Change examine_sym_node() to recursively inspect the members of SYM_STRUCT.
>>> This allows us to simplify lookup_member(): no need to do examine_sym_node(),
>>> the member was already examined.
>>>
>>> This is also good because now ->r_symdef(member) is called on declaration,
>>> not when dissect detects the first usage of ->member.
>>>
>>> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
>> Applied.
>
> Josh, I'll really appreciate if you push your changes to the publicly
> available repository as soon as you post "applied". This way, when I
> have some time for sparse, I read the list, see your post, update sparse
> and see how it's affecting my projects.
>
> If the changes are only available the next day, I'll probably be busy
> with other things.
To the best of my knowledge, I always push out changes before I send the
corresponding "applied" mail. However, I often send the mail a few moments
after pushing out the change, and the kernel.org mirroring processes do not
run the instant I push changes out. In particular, I just confirmed that a
fresh clone of git://git.kernel.org/pub/scm/linux/kernel/git/josh/sparse.git
did not include the changes I've pushed about 8 hours ago today.
The new git.kernel.org server may help alleviate some of the issues that lead
to this high mirroring delay.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-02-28 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 21:37 [PATCH] dissect: simplify lookup_member() Oleg Nesterov
2007-02-27 18:40 ` Josh Triplett
2007-02-28 1:18 ` Pavel Roskin
2007-02-28 2:55 ` Josh Triplett [this message]
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=45E4EF2E.4050101@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.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).