Re: Working copy revision and push pain
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 23, 2008, 14:34 UTC
- Message-ID
- <alpine.LSU.1.00.0803231534050.4353@racer.site>
- In-Reply-To
- <47E668E1.80804@jwatt.org>
Hi,
On Sun, 23 Mar 2008, Jonathan Watt wrote:
Show 10 quoted lines
> Elijah Newren wrote: > > > So, it sounds like we're both saying that in your case, you'd like the > > HEAD become detached and track the sha1 that it previously pointed to > > before your push rather than continuing to track the updated branch. > > Yes, indeed. From my novice perspective it seems like that's absolutely > what should happen, since that's where the working copy came from. > Certainly I see no reason for git-push to leave the working > copy/revision relationship in a bad state.
This is a horrible idea.
If you want to push into non-bare repositories, then please, please, please read the tutorials on that subject.
Thanks, Dscho