Re: [Gnu-arch-users] archive-mirror not pushing cacherevs?

[Dustin Sallings]

On Jan 11, 2004, at 16:09, James Blackwell wrote:

> A) With each revision, we annotate in the revision what the last
>    cacherev was. arch can check that cacherev against the most recent
>    cacherev that exists in the mirror. If it comes across a patch that
>    says it has a newer cacherev than is in the mirror, then perform the
>    cacherev on the mirror. However, we would have to set this up so 
> that
>    multiple new cacherevs could be recorded in a patch.
>
> B) When the user cacherevs a patch, he also performs an essentially
>    empty commit that has for its only purpose to note the existance
>    of a new cacherev.

	I think another alternative would be to not consider a cacherev the 
same way patches are considered.  If they were in a separate place, it 
would be less of an issue to look for different versions on mirror 
(since there should be considerably fewer cached revs than patches).

	It might also be good to have a separate mirror option for digging 
around for cached revs.

	Cacherevs really seem like a different concept to me, as they're an 
optimization for applying patches, and not part of the history of the 
project.  I definitely agree that committed patches or anything else 
directly related to the history of your project (a couple of messages 
after describing having done it) should not be modified.  This is 
definitely one of the parts of arch that makes me the most comfortable. 
 :)

--
SPY                      My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <address@hidden>
|    Key fingerprint =  87 02 57 08 02 D0 DA D6  C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________