Thread (21 messages) 21 messages, 6 authors, 2016-06-15

Re: Recording merges after repo conversion

From: Johan Herland <hidden>
Date: 2016-06-15 22:43:45

On Wednesday 31 October 2007, Johannes Schindelin wrote:
On Wed, 31 Oct 2007, Johan Herland wrote:
quoted
On Wednesday 31 October 2007, Johannes Schindelin wrote:
quoted
All this does not change the fact that installing a graft and 'git gc 
--prune'ing gets rid of the old history.  D'oh.
So will rebasing and --prune'ing, or pulling a rebased branch and 
--prune'ing. Git already gives you _plenty_ of different ropes to hang 
yourself with. The question is whether adding yet another one is worth 
it.
But that is not the question here.  The question here is: are users 
allowed to hang _others_?  I say: no.
Well, to a certain degree (and depending on your level of paranoia), you're 
always responsible for the code entering your own repo, and you could always 
set up a hook disallowing ".gitgrafts" (or whatever it would be called) from 
entering your repo.

But taking this (and everything else that's been said) into account, I totally 
agree with you that adding this feature would open up a _massive_ can of 
worms.


EOD

...Johan

-- 
Johan Herland, [off-list ref]
www.herland.net

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help