[Top][All Lists]

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

[Bug-gnu-arch] [bug #5919] multi-path revision libraries and new hook "c

From: nobody
Subject: [Bug-gnu-arch] [bug #5919] multi-path revision libraries and new hook "cached-revision"
Date: Mon, 13 Oct 2003 11:51:33 -0400
User-agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

=================== BUG #5919: FULL BUG SNAPSHOT ===================

Submitted by: paulinux                Project: GNU arch -- a revision control 
Submitted on: Mon 10/13/2003 at 15:51
Category:  tla                        Severity:  5 - Major                  
Bug Group:  small feature idea        Resolution:  None                     
Status:  Open                         Release:  tla--devo--1.1              
Fixed Release:                        Merge Request?:  yes -- merge from my 
Your Archive Name:  address@hidden/tla--devo--1.1Your Archive Location:         
Assigned to:  None                    

Summary:  multi-path revision libraries and new hook "cached-revision"

Original Submission:  As discussed, as a first step to farewell the inefficient 
pristine trees, we needed multi-path revision libraries and a way to create 
them on demand in an ad-hoc directory.

With sparse revision libraries and the possibility of specifying a path for the 
library commands, the only part missing was how to create and retrieve the 
revision form the desired tree. My choice has been to:

-add a way to exchange information with the hook script via fd 3; the hook 
script can return whatever it need via this fd and the hooks can use as they 
need or just ignore it.

-create a `cached-revision' hook that uses this information to look in the 
returned path for the revision, instead of the default library.

This is implemented in:



A complete description will be posted to the arch-users list.

No Followups Have Been Posted

CC list is empty

No files currently attached

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]