git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "seventh guardian" <seventhguardian@gmail.com>
To: git@vger.kernel.org
Subject: Re: [bug] git-clone over ssh fails when repository has local commits
Date: Sun, 6 Apr 2008 20:02:41 +0100	[thread overview]
Message-ID: <1caff7430804061202x1370d34aw41bf082c8fd4bd64@mail.gmail.com> (raw)
In-Reply-To: <20080406181749.GA2218@coredump.intra.peff.net>

On Sun, Apr 6, 2008 at 7:17 PM, Jeff King <peff@peff.net> wrote:
> On Sun, Apr 06, 2008 at 07:06:40PM +0100, seventh guardian wrote:
>
>  Can you give an exact set of steps to reproduce? There doesn't seem to
>  be anything wrong with those repos, and I was able to do:
>
>   m1$ git clone git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau/
>   m1$ cd xf86-video-nouveau && echo foo >>COPYING && git commit -a -m foo
>   m2$ git clone ssh://m1/path/to/xf86-video-nouveau
>
>  So now my guess is when you make local changes, something funny is going
>  on. Can you describe that process in more detail?

My process is the same as yours, except for the "time-torture" the
repositories have suffered. Surprisingly, everything worked on a fresh
clone. So I suspect my "local master" repo's are somewhat messed up..
Will try to investigate further.

Thanks!
  Renato

      reply	other threads:[~2008-04-06 19:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06 13:45 [bug] git-clone over ssh fails when repository has local commits seventh guardian
2008-04-06 16:11 ` Jeff King
2008-04-06 16:22   ` seventh guardian
2008-04-06 16:56     ` Jeff King
2008-04-06 17:11       ` seventh guardian
2008-04-06 17:51         ` Jeff King
2008-04-06 18:06           ` seventh guardian
2008-04-06 18:11             ` seventh guardian
2008-04-06 20:50               ` Jakub Narebski
2008-04-06 18:17             ` Jeff King
2008-04-06 19:02               ` seventh guardian [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=1caff7430804061202x1370d34aw41bf082c8fd4bd64@mail.gmail.com \
    --to=seventhguardian@gmail.com \
    --cc=git@vger.kernel.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).