Re: [PATCH 4/5] fast-export: do not export negative refs

Sverre Rabbelier [off-list ref] writes:

... In the next commit this will be changed in order
to make sure that 'master..master' does export master.

Sorry, but you need to be much more clear why this could be a good
thing.

Everywhere in git a range A..B means "reachable from B but exclude
everything that is reachable from A", and with that knowledge it is
natural to expect that master..master should yield an empty set. If you
need to change it for some reason, we need to know why, and if you are
doing it for a narrow special case, we need to know why that case is so
special.

Hi Junio,

On Sun, 24 Jul 2011, Junio C Hamano wrote:

Sverre Rabbelier [off-list ref] writes:

quoted

... In the next commit this will be changed in order to make sure that 
'master..master' does export master.

Sorry, but you need to be much more clear why this could be a good 
thing.

Maybe we should have written 'master^0..master' or 'blub..blah' where 
'blah' points to the same commit as 'blub'.

The problem is that we need to be able to tell which _ref_ is 
uninteresting, not which _commit_, since one and the same commit can be 
referenced by an uninteresting and an interesting ref.

Hopefully you will excuse our being a little incoherent after a codathon,
Dscho