From: Jan Hudec <bulb@ucw.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git bug/feature request
Date: Fri, 30 Nov 2007 19:21:21 +0100 [thread overview]
Message-ID: <20071130182121.GC30048@efreet.light.src> (raw)
In-Reply-To: <figv47$926$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Tue, Nov 27, 2007 at 12:30:16 +0100, Jakub Narebski wrote:
> gapon wrote:
>
> > hi all,
> > first of all i don't know if there's a bugzilla or something similar
> > for git - i have found just this email (on http://git.or.cz/ webpage).
>
> There isn't any bug tracker for git. Use git mailing list for bug
> reports and feature requests.
>
> > i have discovered "weird" behaviour of git in this scenario*:
> > - user A is working in repo A
> > - user B clones repo A
> > - user B makes some changes, commits, pushes
>
> Do not push into checked out branch!
Push is the only non-local operation, that could break the checked out state,
right? Than it should be possible to add a check that a push is trying to
change the checked-out ref and detach the HEAD if so.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-30 18:21 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
2007-11-27 16:36 ` Alex Riesen
2007-11-27 11:30 ` Jakub Narebski
2007-11-30 18:21 ` Jan Hudec [this message]
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=20071130182121.GC30048@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=jnareb@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).