Re: Working copy revision and push pain

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Sun, 23 Mar 2008, Jonathan Watt wrote:

> 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

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux