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

RE: Question about applying patches

From: Wayne Johnson <wayne_at_zk.com>
Date: Wed, 25 Jun 2014 14:06:12 -0700

> >
> > I really think this is the best method for you to use anyway.
> You are probably right. There's one other reason I don't do this,
> which I hadn't mentioned before, because it's not a great reason: If I
> use a branch, the whole world can see my incomplete work. If I keep
> them local they're only visible to me. This is mainly a matter of
> vanity (I'd rather not let the world see how stupid I can be), and
> partly that I feel that log messages that are visible to everyone,
> should be understandable by everyone: and those are harder to write.

I have a similar issue. We use an issue tracker that shows every revision
as an candidate for code review. I like to check in frequently and this
was generating a lot of 'noise' in the tracker.

I solved this problem by turning my SVN working copy into a git repo. I
leave my git 'master' in sync with SVN and work on a branch and merge my
branch into 'master' when I am ready to check into SVN.

For backup I have a remote git repository that I push to frequently. It's
actually quite convenient.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-06-25 23:06:33 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.