[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: issue 2274

From: Vivek <vivek_at_collab.net>
Date: 2005-04-18 15:09:42 CEST

On Mon, 2005-04-18 at 18:34, Peter N. Lundblad wrote:
> On Mon, 18 Apr 2005, Vivek wrote:
>
> > Will a single line addition in svn_opt_subcommand_desc_t
> > svn_cl__cmd_table[] for update suffice?
> >
> > Like
> > A Added\n"
> > " D Deleted\n"
> > " U Updated\n"
> > " C Conflict\n"
> > " G Merged\n"
> > " B Broken Lock Token\n" <--new
> >
> > Or is there something that I have overlooked?
>
> I think something like "A B in the third column...", so you don't mix it
> up with the status codes for the other two columns.
Yes, But the other lines are so cryptic. I thought I was generous enough
to give three words for B. :-)

> You may want to write
> it in a way that makes clear that this isnt just when the lock was Broken,
> but also when it is stolen, i.e. the lock is defunct and not valid in the
> repository any longer. (Note how I delibarately avoid giving an exact
> wording:-)
B Broken or Stolen Lock?
>
Thanks
> Regards,
> //Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 18 15:30:13 2005

This is an archived mail posted to the Subversion Dev mailing list.