thanks very much for your patience. this question isn't really about the
svnClientAdapter.jar per se, though i can see i was not clear. it's
about identifying discrete moments in time in the subclipse & subversion
projects generally. i see you're getting ready to release a .9.28
sometime shortly. when you publish that, how will i be able to identify
-exactly- which set of source files compose that release?
clearcase, for example, allows me to label a set of files, and the label
can be used to identify a release. there is no labeling capacity in
subversion, of which i'm aware (-please- correct me if i'm wrong). the
documentation recommends using branches to represent discrete moments in
this question is important because i'd like to address issues i find in
the subclipse plugin by contributing my fixes back to the subclipse
project, which i've done already. pulling HEAD can result in side
effects, like pulling in new bugs, disrupting my ability to help fix
problems. when you create .9.28, it would be great if we can get a
source drop along with the plugin, or if you could create a named branch
in the source tree.
again, thanks very much for your patience.
> -----Original Message-----
> From: Mark Phippard [mailto:MarkP@softlanding.com]
> Sent: Friday, February 04, 2005 5:49 PM
> To: email@example.com
> Subject: RE: Re: svnClientAdapter not building due to javasvn
> > sorry if this is a dumb question, but what do you mean 'look at the
> > revision number and then extrapolate'? the revision number for what?
> You could either look at the revision number when the tag was
> created, or
> even the revision number that corresponds the
> svnClientAdapter.jar file in
> the core project. Armed with that revision number, you can
> then look at
> the svnClientAdapter project and you know that commits after
> that revision
> number are not included. It is also relatively likely that
> commits before
> that revision are included.
> Scanned for SoftLanding Systems, Inc. by IBM Email Security
> Management Services powered by MessageLabs.
> To unsubscribe, e-mail: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
Received on Mon Feb 28 11:56:41 2005