[Reportbug-maint] VCS metadata noise

Sandro Tosi matrixhasu at gmail.com
Wed Jul 2 14:22:52 UTC 2008

On Wed, Jul 2, 2008 at 16:15, Ben Finney <ben+debian at benfinney.id.au> wrote:
> What I said was:
>> > > > So, for this particular bad bug, I went with the tool that let
>> > > > me fix the bug, rather than fighting the VCS tool.
> Thus, it was the fact that I used a VCS tool that I didn't have to
> fight with which enabled me to focus my workflow on fixing the bug.
> (If it's this that you want to discuss, I doubt we need to go over it
> here. There are innumerable discussions online about the merits of
> different VCSes. My only point here is that *for me* it was much
> simpler to use Bazaar than the Subversion client.)
> Since fixing this particular bug quickly and properly was (in my
> assessment) quite important, I decided to use the tools that would get
> me there with the least friction. The tradeoff was that the friction
> was deferred to the commit into the Subversion repository, with the
> result being this thread.
> That tradeoff is unlikely to be attractive in most cases, so you're
> unlikely to see this happen much in future.

So (first 2 command if you don't have a local copy already, if so
replace with "svn up"):

$ svn checkout svn://....<the path to the team repo>/trunk reportbug
$ cd reportbug
$ <change the code>
$ svn up
$ svn ci

is really that harder than the "workflow" you're using? Ben, really,
use svn, there's no fighting just read the manpage and start using it.
you fear doing something wrong? there's revert, checkout from a given
revision and all other shiny stuff to fix if that will happen.

Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

More information about the Reportbug-maint mailing list