sm-sorcery-bugs AT lists.ibiblio.org
Subject: Bugs for Sorcery are reported here
List archive
[SM-Sorcery-Bugs] [Bug 10717] New: scribe update from perforce
- From: bugzilla-daemon AT bugs.sourcemage.org
- To: sm-sorcery-bugs AT lists.ibiblio.org
- Subject: [SM-Sorcery-Bugs] [Bug 10717] New: scribe update from perforce
- Date: 16 Mar 2006 15:00:45 -0000
http://bugs.sourcemage.org/show_bug.cgi?id=10717
Summary: scribe update from perforce
Product: Sorcery
Version: Untargetted future release
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: Scribe
AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
ReportedBy: dkowis AT shlrm.org
I don't know about most of the developers, but I keep the entire grimoire tree
in p4 on my client. It would be a nice feature, and would cut back on
bandwidth
usage, if I could:
scribe update test from dkowis@p4://home/dkowis/p4-smgl/grimoires/test
or something.
It would then su to that user, `run p4 sync
/home/dkowis/p4-smgl/grimoires/test/...` and then create a grimoire tarball
and
proceed with the standard scribe process. So on a scribe update the same thing
would happen without having to type in all the stuff.
Basically what I'm going for is the ability to use my client view to generate
a
grimoire. I know I could do this with a tarball, but then I don't have scribe
update capability.
As I type I doubt the validity of this request (might be too scm specific),
but
I'm gonna file it anyway.
--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
- [SM-Sorcery-Bugs] [Bug 10717] New: scribe update from perforce, bugzilla-daemon, 03/16/2006
Archive powered by MHonArc 2.6.24.