History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEABKL-5316
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Dmitry Jemerov
Reporter: Keith Lea
Votes: 0
Watchers: 0
Available Workflow Actions

Mark as Stalled
Operations

If you were logged in you would be able to see more operations.
IDEA: Backlog

Add option to run argument-less "p4 sync" instead of syncing particular folders

Created: 19 Oct 07 00:13   Updated: 19 Oct 07 19:39
Component/s: Version Control Integration. Perforce
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Linux

Build: 7,346
Severity: Medium


 Description  « Hide
Syncing specific folders is discouraged here - everything is supposed to be synced to the same CL. This means users cannot use VCS->Update Project, as it seems to only run p4 sync on particular folders. I'd like an option to just run plain old p4 sync without any arguments.

 All   Comments   Work Log   Change History      Sort Order:
Dmitry Jemerov - 19 Oct 07 13:50
This is one more option that is best handled by patching your version of the Perforce plugin rather than cluttering the main one with options that are very specific to particular workflows.

Keith Lea - 19 Oct 07 19:34
Fair enough.. I'd actually be surprised if most companies sync individual folders like IntelliJ does. Is this what you guys do? Do you ever do an argless p4 sync?

Dmitry Jemerov - 19 Oct 07 19:39
Our Perforce depot contains multiple projects, and many developers have more than one project in their clientspec, but actively work with only one project. So an argless p4 sync would often pull much more stuff than actually needed.