git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gapon <gapon007@gmail.com>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git bug/feature request
Date: Tue, 27 Nov 2007 14:45:47 +0100	[thread overview]
Message-ID: <200711271445.47695.gapon007@gmail.com> (raw)
In-Reply-To: <81b0412b0711270503s7e69be3bn151cfa58b8067f35@mail.gmail.com>

Dne úterý 27 listopadu 2007 Alex Riesen napsal(a):
> On 27/11/2007, gapon <gapon007@gmail.com> wrote:
> > as i wrote in my first email - i know that this is not "correct" scenario
> > (i don't and won't use it anywhere) - but the git's behaviour is in such
> > case confusing, at least for me
> > just for clarification - my email wasn't about how to push or create
> > shared repository - it was just about what i have discovered while
> > playing with different scms
>
> Well... It is known problem, for one. That user B of yours, did he just
> cloned user A's repo?

yes, i can paste here all the scenario step by step if you want
>
> What I suspect is a change in how git-clone setups the cloned repo
> could have taken care of it. We could either setup push-configuration
> so that it just does not work (and let user change to his preference),
> or somehow figure out where the pushed references can safely land
> and put that in the cloned repo configuration (that is "SOMEHOW",
> I afraid. Absolutely no idea what could that be).

hard to say what to do, what is correct - now i would say that i like hg 
behaviour the most - but i can be wrong of course; the only purpose of this 
discussion is that i have found out (by accident ;) "weird" behaviour of git 
in such situation - and because git is definitely my most favorite scm i 
wanted to report bug/feature/whatever

thanks for all your comments guys

  reply	other threads:[~2007-11-27 13:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 10:27 git bug/feature request gapon
2007-11-27 10:57 ` Benoit Sigoure
2007-11-27 11:16   ` gapon
2007-11-27 11:51     ` Jakub Narebski
2007-11-27 12:50       ` gapon
2007-11-27 13:31         ` Jakub Narebski
2007-11-27 13:38           ` Jakub Narebski
2007-11-27 14:06           ` gapon
2007-11-27 11:21 ` Alex Riesen
2007-11-27 11:31   ` gapon
2007-11-27 13:03     ` Alex Riesen
2007-11-27 13:45       ` gapon [this message]
2007-11-27 16:36         ` Alex Riesen
2007-11-27 11:30 ` Jakub Narebski
2007-11-30 18:21   ` Jan Hudec
2007-11-27 14:35 ` Peter Karlsson
2007-11-27 14:38   ` David Kastrup
2007-11-28 13:30     ` Peter Karlsson
2007-11-27 15:13   ` Jakub Narebski
2007-11-27 19:49     ` Steven Grimm
2007-11-27 20:19       ` Daniel Barkalow
2007-11-27 20:34 ` Daniel Barkalow

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=200711271445.47695.gapon007@gmail.com \
    --to=gapon007@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@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).