[p4] perforce vs. subversion
Sam Roberts
sroberts at bycast.com
Wed May 3 11:52:38 PDT 2006
On Wed, May 03, 2006 at 06:45:58PM +0100, Sweeney, Tony wrote:
> > I used to change these conf files and not open them, but "p4 diff"
> won't
> > report differences on unopened files!
>
> Uh, "don't do that then"?
"used to"
I don't anymore, and diff works, but I have the problem of keeping my
discardable changes out of the current changelist.
> P4 diff -f filename#have does what you want.
Thanks, I will try this.
> > Also, the "p4 submit" commmand (unlike svn) doesn't allow multiple
> > arguments. So if you have changes in src/ and doc/, but don't want to
> > submit changes in conf/, you have to do a "p4 submit ...", then
> manually
> > weed out the conf/ files. With svn, I would do "svn submit src doc".
>
> 'P4 submit' didn't originally take any arguments at all. I asked them
> to add one, on the grounds I often found myself running 'p4 edit
> filename; p4 submit filename', and it seemed like a fairly natural
> usage.
I'd agree.
> file names, triggering a bug, which Perforce "fixed" by restricting the
> number of arguments to one (although wildcards are still allowed). In
> my view it should take arbitrary files on the command line, same as p4
> edit, etc. As a workround, you can create a change using 'p4 change',
> put just the files you want into it using 'p4 reopen -c <changeno>
> files' (which doesn't have the single argument restriction imposed by
> submit) and 'p4 submit -c <changeno>'.
Thanks for the info.
I'm not yet convinced that this is easier or more reliable than just
deleting files from the changelist when I do a p4 submit, but I'll give
it a try.
Thanks,
Sam
More information about the perforce-user
mailing list