[p4] perforce vs. subversion

[Bennett, Patrick]

...and Perforce can't do this via the submit command, why??  :\

I had to add the submit [options] [filename(s)] feature ourselves via my
Ruby wrapper script.
I never should have to do it though.  It's pretty basic functionality
that Perforce should already handle.   :(



> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Weintraub, David
> Sent: Thursday, May 04, 2006 9:05 AM
> To: perforce-user at perforce.com
> Subject: Re: [p4] perforce vs. subversion
> 
> > > Also, the "p4 submit" command (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.
> 
> There's a way around this:
> 
>     $ p4 change
>     Change 8640 created.
>     $ p4 reopen -c 8640 src/... doc/...
>     $ p4 submit -c 8640
> 
> This will submit all the files in src and doc, but not in conf.
>