From: Jeff King <peff@peff.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Paul Tarjan <ptarjan@gmail.com>, git@vger.kernel.org, yury239@gmail.com
Subject: Re: Git Confusion
Date: Fri, 29 May 2009 09:52:42 -0400 [thread overview]
Message-ID: <20090529135242.GA30926@coredump.intra.peff.net> (raw)
In-Reply-To: <m3d49sauru.fsf@localhost.localdomain>
On Fri, May 29, 2009 at 06:44:26AM -0700, Jakub Narebski wrote:
> > Usually such a repo is bare, and gets updates only by push. In that
> > case, enabling the update hook to run update-server-info is sufficient.
> > But in your case, you are actually working on the remote repo via commit
> > and other means, so there is no convenient way to always
> > update-server-info after a change.
>
> Well, he can always add git-update-server-info to post-commit hook.
That covers committing, but what about reset, rebase, "branch -f", etc?
I don't think there is a catch-all for all the ways that a repo can be
updated locally.
> > Is there a particular reason you cloned over http instead of over ssh?
> Or git protocol?
Yes, that would work fine, too. I mentioned ssh because he already
indicated that he was able to ssh into the box (and may or may not have
the git daemon set up).
-Peff
next prev parent reply other threads:[~2009-05-29 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 7:43 Git Confusion Paul Tarjan
2009-05-29 12:58 ` Jeff King
2009-05-29 13:44 ` Jakub Narebski
2009-05-29 13:52 ` Jeff King [this message]
2009-05-29 20:24 ` Paul Tarjan
2009-05-29 20:28 ` Avery Pennarun
2009-05-29 20:38 ` Jeff King
2009-05-30 0:41 ` Sitaram Chamarty
2009-05-29 20:45 ` Jakub Narebski
2009-05-30 1:32 ` Sitaram Chamarty
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=20090529135242.GA30926@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=ptarjan@gmail.com \
--cc=yury239@gmail.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;
as well as URLs for NNTP newsgroup(s).