Re: Recording merges after repo conversion

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

 



Hi,

On Wed, 31 Oct 2007, Peter Karlsson wrote:

> > Yes!  Of course!  If what you want becomes possible, I could make an 
> > evil change in history long gone, and slip it by you. You could not 
> > even see the history which changed.
> 
> I would see the grafts file being changed, which would alert me (the 
> problem I have with graft is that it *replaces* history information for 
> an element, not just *add* to it, which threw me off at my first attempt 
> at creating one).

The thing is: it is too easy to overlook a tiny change like this.  And it 
is very, very difficult to see what it _really_ changed.

Therefore I am _strongly_ opposed to changing the current behaviour.

> > You can do that already.  But you have to ask the people at the other 
> > end to actually apply the graft.
> 
> Last time I tried, git would not add files that was in the ".git" 
> subdirectory to version control. I might have done something 
> incorrectly, though, so I'll see if it works now.

Well, I was not explicit enough.  You can check in the grafts file _under 
a different name_.  Outside of .git/.

Hth,
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