From: Michael Buesch <mb@bu3sch.de>
To: Pavel Roskin <proski@gnu.org>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: More breakage in wireless-dev.git
Date: Sat, 17 Feb 2007 19:30:10 +0100 [thread overview]
Message-ID: <200702171930.10830.mb@bu3sch.de> (raw)
In-Reply-To: <20070217132614.zfbt6sckkogosss8@webmail.spamcop.net>
On Saturday 17 February 2007 19:26, Pavel Roskin wrote:
> Quoting Michael Buesch <mb@bu3sch.de>:
>
> > On Saturday 17 February 2007 19:10, Pavel Roskin wrote:
> > > Awesome! I'm waiting for your public repository to update so I can test
> > your
> > > fixes.
> >
> > I always update that when committing stuff, directly.
> > So when you see mail from me "I committed foo", it means it's
> > available in the public repository.
>
> Then you are not running git-update-server-info every time from
> hooks/post-update. It needs to be run every time any of the branch heads
> changes, i.e. on every git-push. The git documentation was unclear about it
> until recently.
Uh, why? I thought it is just an optimization and
git walks the tree, if the server info is not updated.
But I ran it manually now.
--
Greetings Michael.
next prev parent reply other threads:[~2007-02-17 18:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 5:41 More breakage in wireless-dev.git Pavel Roskin
2007-02-17 8:06 ` Pavel Roskin
2007-02-17 13:02 ` Michael Buesch
2007-02-17 16:44 ` Pavel Roskin
2007-02-17 16:55 ` Michael Buesch
2007-02-17 17:30 ` Michael Buesch
2007-02-17 17:51 ` Pavel Roskin
2007-02-17 17:56 ` Michael Buesch
2007-02-17 18:10 ` Pavel Roskin
2007-02-17 18:14 ` Michael Buesch
2007-02-17 18:26 ` Pavel Roskin
2007-02-17 18:30 ` Michael Buesch [this message]
2007-02-17 18:58 ` Pavel Roskin
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=200702171930.10830.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@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 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.