- Appended to comment:
drh added on 2009-11-06 14:06:02:
This already works. Just type:fossil open REPOSITORYNAME BRANCHNAME
- Change resolution to "Overcome_By_Events"
- Change status to "Closed"
- Change comment to "I would like to see a flag added to the "open" command that makes it possible to specify which branch or version is to be written out on the initial checkout. When an initial checkout is done using the "open" command, the command's behavior in terms of which branch is checked out is undocumented. Observation suggests that the checked-out branch is the last one to have something checked in to it. If that's not the desired branch then an extra action is required, like using the "checkout" command. I would like to a) save a step and b) be very conservative about what code appears on my drive. If I'm deploying to a production server, I don't want non-vetted code to be written out, even transiently. A failure anywhere along the deploy process might leave exploitable code or sensitive information lying about. Thus I would like to be able to specify the branch/version used by the open command so as to have complete control at all times over what code exists in my checkout directory."
- Change private_contact to "22e3b7a55e291d179313f4c2e34877f09743ee31"
- Change severity to "Important"
- Change status to "Open"
- Change title to "make it possible to specify branch with "open" command"
- Change type to "Feature_Request"