Re: [PATCH] git-svn: handle our top-level path is deleted and later re-added

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Dec 14, 2007 at 08:39:09AM -0800, Eric Wong wrote:
> Previously, git-svn would ignore cases where the path we're
> tracking is removed from the repository.  This was to prevent
> heads with follow-parent from ending up with a tree full of
> empty revisions (and thus breaking rename detection).
> 
> The previous behavior is fine until the path we're tracking
> is re-added later on, leading to the old files being merged
> in with the new files in the directory (because the old
> files were never marked as deleted)
> 
> We will now only remove all the old files locally that were
> deleted remotely iff we detect the directory we're in is being
> created from scratch.
> 
> Thanks for Marcus D. Hanwell for the bug report and
> Peter Baumann for the analysis.
> 
> Signed-off-by: Eric Wong <normalperson@xxxxxxxx>
[...]

It seems to solve the problem seen in the avogadro repo. At least
the suspicious revisions I checked looked identical in the imported
version.

-Peter
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux