There's no accounting for users! (Not that I qualify yet...)

The problem with using a VCS to do backup is that you have to rely on
the users to do it, backups should run independently of the user.
It's guaranteed given time that some project or code will end up bring
useful but not committed and subsequently lost.
Really only units of work or discreet changes should be committed,
rather than the end of the last bug fix and the start of the next.

Without getting too sidetracked can anyone answer my original


On Jul 8, 1:09 pm, Konstantin Khomoutov
<> wrote:
> On Fri, 8 Jul 2011 03:55:15 -0700 (PDT)
> Craig <> wrote:
> > I'm using svn at my workplace and am looking at git to help with some
> > off-line working issues.
> > Besides off-line working we also have problems with svn when storing
> > local copies on mapped network drives.
> > This is a known issue with svn and not recommended, but makes backups
> > much easier.
> > Can git working copies be stored on windows network drives?
> Git devs put a lot of effort to make Git work light-fast with the local
> filesystem and then you're trying to defeat this advantage.
> This problem (backups) should be solved by providing each developer its
> private bare repo on a centralised server (or servers) and issuing a
> policy according to which every programmer must push whaveter changes
> she recorded so far to that private repo before leaving home, that's
> all.  Git has no problem at all with using several "remotes".  You can
> even push to another hard disk this way etc.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to