From: Andy Whitcroft <apw@shadowen•org>
To: "Shawn O. Pearce" <spearce@spearce•org>
Cc: git@vger•kernel.org
Subject: Re: Pushing into a repository with working directory?
Date: Fri, 05 Jan 2007 08:51:14 +0000 [thread overview]
Message-ID: <459E1182.201@shadowen.org> (raw)
In-Reply-To: <20070102045108.GC27690@spearce.org>
Shawn O. Pearce wrote:
> So tonight on #git I think I answered for the 10th time why the
> working directory doesn't update after a push to its associated
> repository.
>
> We all know its somewhat dangerous to push into the current branch
> of a working directory, especially if that working directory contains
> uncommitted changes, as HEAD no longer matches the index.
>
> But we all also know its incredibly useful to be able to push into
> a repository with a working directory, so we certainly don't want
> to disallow it entirely.
>
> What about refusing a push to the current branch (branch listed in
> $GIT_DIR/HEAD) and the repository appears to have a working directory
> (is_bare_git_dir is false)?
Special casing the 'current' branch makes any sort of automated push
setup unreliable. Indeed the special case preventing a fetch into the
current branch is pretty annoying for the same reason. I would almost
prefer to relax that than add the same for push.
-apw
next prev parent reply other threads:[~2007-01-05 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 4:51 Pushing into a repository with working directory? Shawn O. Pearce
2007-01-05 8:51 ` Andy Whitcroft [this message]
2007-01-05 8:54 ` Junio C Hamano
2007-01-05 9:32 ` Andy Whitcroft
2007-01-05 9:50 ` Junio C Hamano
2007-01-05 19:36 ` Shawn O. Pearce
2007-01-08 13:53 ` Andy Whitcroft
2007-01-09 0:57 ` Junio C Hamano
2007-01-09 3:32 ` Shawn O. Pearce
2007-01-09 9:15 ` Andreas Ericsson
2007-01-09 13:51 ` Johannes Schindelin
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=459E1182.201@shadowen.org \
--to=apw@shadowen$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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